C and C++ - preprocess, compile, load, run - what each step is for
Archive - Originally posted on "The Horse's Mouth" - 2011-04-12 11:23:12 - Graham EllisC and C++ original source code goes through a number of steps on its way to becoming a runnable program.
1. The C Preprocessor is run on the original source. This takes the source lines that start with a # character and acts on them as directed. (It does a bit more too - more about that anon!)
2. The C / C++ compiler takes the source code as modified by the preprocessor and converts it into a section of object code. That's the instructions for actually running on the target computer's processor, although not actually in a runnable form yet.
3. The Link loader / Task Builder then takes a whole set of object code files - both te ones written by you (the programmer) and others from standard libraries, and couples them up into a single executable file. Some of the standard stuff may not actually be copied into the executable; that executable may just include a note of where it may be found at run time.
4. At run time, the executable file is loaded into memory and run; part of that loading may be changing the memory addresses that the program runs at (on a multiprocess computer, there's no way at build time of knowing what else will be running at the same time), and pulling in code from the libraries which may have just been 'earmarked' at stage 3.
The directives at stage 1 may include:
#include - to bring in another text file at this point
#define - to define a flag or string for replacement in this phase
#ifdef - to mark the following code to be included in the output source ONLY if a specific flag variable / string has been defined
#ifndef - to mark the following code to be included in the output source ONLY if a specific flag variable / string has NOT been defined
#endif - to mark the end of a conditional inclusion block started by #ifdef or #ifndef
There's an example showing the uses of these [here] in a short C program from last week's C Course, and you'll also find them extensively used in C++ to bring in header files into main application programs (see [example]) ... and then within the header files of the classes to bring in the header files of the classes on which they are based (See [example]). You'll notice the use of defined preprocessor constants in this example to ensure that headers aren't double defined ... in the pet.h header file you'll find you have:
#ifndef PET
#define PET 1
definition lines
#endif