c++编译器和链接器（C + + compiler and linker）.docVIP

c++编译器和链接器（C + + compiler and linker） Some people write C/C + + (which is supposed to be C + +) programs and are overwhelmed by the error of the unresolved external link or duplicated external simbol (because the error message cannot be located in a single line). Or some parts of the language do not know why (or not) to design. After you know this article, there may be some answers. Lets start by looking at how we write a program. If youre using some kind of IDE (Visual Studio, Elicpse, Dev c + +, etc.), you may not be able to find how the program is organized (a lot of people are against the beginner using the IDE). Because using an IDE, what you do is create a new set of CPP and.h files in a project, and then click compile in the menu, and everything is fine. But in the past, programmers didnt write that way. They first have to open an editor, write the code like a text file, and then click on the command line Cc 1. CPP - o 1. O Cc 2. CPP - o 2. O Cc 3. CPP - o 3. O Cc here represents a C/C + + compiler, followed by CPP file to compile, and with the -o to output the specified file (please forgive me for not using any popular compiler, for example). This is where the current directory will appear: (1) o (2) o (3) o Finally, the programmer has to type Link 1. O 2. O 3. O - o a.ut To generate the final executable a.ut. The current IDE, in fact, follows this step, but automates everything. Lets analyze the process above and see what we can find. First, the source code is compiled separately from each CPP file. For each compilation, if in the case of the CPP file include other CPP file (this is wrong written in c + + code), then the compiler only know current that a CPP file to compile, for the presence of other CPP file completely. Second, after each CPP file is compiled, the resulting.o file is read by a link to generate executable files. Well, with these perceptual knowledge, lets look at how C/C + + programs are organized. First, some concepts: Compilation: the com