C Shells by the Seashore

The vast majority of end user interactions with technology comes in the form of graphical user interfaces, or GUIs, for short. On the other hand, most of the interactions the developers of these interfaces use to create the content the end user enjoys (or plods through the workday) using is done using a command line interface, or CLI, for short. The difference between the two is simple: a GUI gives a person the ability to have interactions with a device via graphical depictions of programming code, while someone using a CLI interacts with a device via text known as instructions given to the device.


In this post, I’m going to introduce each step of compilation in the shell using the C programming language.


Compilation occurs in four steps — first, preprocessing, second, compilation, third, assembler, and fourth, linking.

In the preprocessing stage, commands written in a programming language are combined with preprocessor commands.

In the compiling stage, all the code and programming files in the project are turned into an object file.

In the assembling stage, the object file is then converted from human readable language to computer readable language.

In the linking stage, the object files created by the compiler and predefined library objects are used to create an executable file.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.