Compiler - Revision history

Chili: /* See also */

2017-03-26T08:29:29Z

‎See also

Chili at 08:29, 26 March 2017

2017-03-26T08:29:09Z

Chili: /* The Linker */

2016-08-01T02:48:09Z

‎The Linker

Chili: /* The Linker */

2016-08-01T02:47:37Z

‎The Linker

Chili: /* The Details */

2016-08-01T02:46:54Z

‎The Details

Chili: /* The Details */

2016-08-01T02:45:11Z

‎The Details

Chili: /* The Details */

2016-08-01T02:33:03Z

‎The Details

Chili at 02:32, 1 August 2016

2016-08-01T02:32:44Z

Chili at 02:32, 1 August 2016

2016-08-01T02:32:23Z

Chili at 02:30, 1 August 2016

2016-08-01T02:30:57Z

← Older revision		Revision as of 08:29, 26 March 2017
Line 18:		Line 18:

	== See also ==		== See also ==
−	* [[Beginner C++ Game Programming Tutorial 19\|Beginner C++ Game Programming Tutorial 19 (Compiler Confessions)]]	+	* [[Beginner C++ Game Programming Tutorial 18\|Beginner C++ Game Programming Tutorial 18 (Compiler Confessions)]]

← Older revision		Revision as of 08:29, 26 March 2017
Line 16:		Line 16:
	== Visual C++ Compiler ==		== Visual C++ Compiler ==
	The compiler in Visual Studio is named <code>cl.exe</code>, and the linker is named <code>link.exe</code> (<code>cl64.exe</code> and <code>link64.exe</code> for the 64-bit versions). If you're feeling especially masochistic you can try building some code from the command line. Also included is the assembler <code>ml.exe</code>. Proceed at your own peril ;)		The compiler in Visual Studio is named <code>cl.exe</code>, and the linker is named <code>link.exe</code> (<code>cl64.exe</code> and <code>link64.exe</code> for the 64-bit versions). If you're feeling especially masochistic you can try building some code from the command line. Also included is the assembler <code>ml.exe</code>. Proceed at your own peril ;)
		+
		+	== See also ==
		+	* [[Beginner C++ Game Programming Tutorial 19\|Beginner C++ Game Programming Tutorial 19 (Compiler Confessions)]]

@@ Line 10: / Line 10: @@
 == The Linker ==
-The linker has two main jobs: 1) take all the .obj files and jam them into one file (the .exe) and 2) link all the function call addresses to their destinations. You see, when the compiler is translating a function call into machine language, it won't know the address to jump to for the call if its in a different translation unit (.cpp file) because the compiler is only aware of the current translation unit it's working on, so the compiler leaves the address blank and the linker then fills that in afterwards.
+The linker has two main jobs: 1) take all the .obj files and jam them into one file (the .exe) and 2) link all the function call addresses to their destinations. You see, when the compiler is translating a function call into machine language, it won't know the address to jump to for the call if its in a different translation unit (.cpp file) because the compiler is only aware of the current translation unit it's working on, so the compiler leaves the addresses blank and the linker then fills them in afterwards.
 Besides .obj files, the linker also accepts library (.lib) files as inputs. There's nothing special about .lib files, all they are is a bunch of .obj files jammed together for easy organization.

@@ Line 10: / Line 10: @@
 == The Linker ==
-The linker has two main jobs: 1) take all the .obj files and jam them into one file and 2) link all the function call addresses to their destinations. You see, when the compiler is translating a function call into machine language, it won't know the address to jump to for the call if its in a different translation unit (.cpp file) because the compiler is only aware of the current translation unit it's working on, so the compiler leaves the address blank and the linker then fills that in afterwards.
+The linker has two main jobs: 1) take all the .obj files and jam them into one file (the .exe) and 2) link all the function call addresses to their destinations. You see, when the compiler is translating a function call into machine language, it won't know the address to jump to for the call if its in a different translation unit (.cpp file) because the compiler is only aware of the current translation unit it's working on, so the compiler leaves the address blank and the linker then fills that in afterwards.
 Besides .obj files, the linker also accepts library (.lib) files as inputs. There's nothing special about .lib files, all they are is a bunch of .obj files jammed together for easy organization.

@@ Line 2: / Line 2: @@
 == The Details ==
-To be completely accurate, the compiler by itself doesn't output the .exe file. That's done by a separate program called a [[#the%20linker|linker]]. The compiler processes each .cpp file in your project, turning your C++ statements into machine code that the CPU can understand, and outputs an .obj (object) file that contains machine language instructions for each .cpp file processed. The linker then jams all the objects together and links up the function calls, outputting that sweet, sweet binary executable.
+To be completely accurate, the compiler by itself doesn't output the .exe file. That's done by a separate program called a [[#The Linker|linker]]. The compiler processes each .cpp file in your project, turning your C++ statements into machine code that the CPU can understand, and outputs an .obj (object) file that contains machine language instructions for each .cpp file processed. The linker then jams all the objects together and links up the function calls, outputting that sweet, sweet binary executable.
-Now compilation of a .cpp file generally proceeds in two phases. The first phase is called 'preprocessing', and we generally say that this is carried out by the '[[#the%20preprocessor|preprocessor]]', although in actuality there is no separate program for the preprocessor, it's just a routine run by the compiler. After preprocessing, the compilation proper begins and an .obj file is pooped out. Other files with metadata for debugging purposes etc. may also be pooped out.
+Now compilation of a .cpp file generally proceeds in two phases. The first phase is called 'preprocessing', and we generally say that this is carried out by the '[[#The Preprocessor|preprocessor]]', although in actuality there is no separate program for the preprocessor, it's just a routine run by the compiler. After preprocessing, the compilation proper begins and an .obj file is pooped out. Other files with metadata for debugging purposes etc. may also be pooped out.
 == The Preprocessor ==

@@ Line 4: / Line 4: @@
 To be completely accurate, the compiler by itself doesn't output the .exe file. That's done by a separate program called a [[#the linker|linker]]. The compiler processes each .cpp file in your project, turning your C++ statements into machine code that the CPU can understand, and outputs an .obj (object) file that contains machine language instructions for each .cpp file processed. The linker then jams all the objects together and links up the function calls, outputting that sweet, sweet binary executable.
-Now compilation of a .cpp file generally proceeds in two phases. The first phase is called 'preprocessing', and we generally say that this is carried out by the [[#the preprocessor|preprocessor]], although in actuality there is no separate program for the preprocessor, it's just a routine run by the compiler. After preprocessing, the compilation proper begins and an .obj file is pooped out. Other files with metadata for debugging purposes etc. may also be pooped out.
+Now compilation of a .cpp file generally proceeds in two phases. The first phase is called 'preprocessing', and we generally say that this is carried out by the '[[#the preprocessor|preprocessor]]', although in actuality there is no separate program for the preprocessor, it's just a routine run by the compiler. After preprocessing, the compilation proper begins and an .obj file is pooped out. Other files with metadata for debugging purposes etc. may also be pooped out.
 == The Preprocessor ==

@@ Line 2: / Line 2: @@
 == The Details ==
-To be completely accurate, the compiler by itself doesn't output the .exe file. That's done by a separate program called a linker. The compiler processes each .cpp file in your project, turning your C++ statements into machine code that the CPU can understand, and outputs an .obj (object) file that contains machine language instructions for each .cpp file processed. The linker then jams all the objects together and links up the function calls, outputting that sweet, sweet binary executable.
+To be completely accurate, the compiler by itself doesn't output the .exe file. That's done by a separate program called a [#the linker|linker]. The compiler processes each .cpp file in your project, turning your C++ statements into machine code that the CPU can understand, and outputs an .obj (object) file that contains machine language instructions for each .cpp file processed. The linker then jams all the objects together and links up the function calls, outputting that sweet, sweet binary executable.
-Now compilation of a .cpp file generally proceeds in two phases. The first phase is called 'preprocessing', and we generally say that this is carried out by the 'preprocessor', although in actuality there is no separate program for the preprocessor, it's just a routine run by the compiler. After preprocessing, the compilation proper begins and an .obj file is pooped out. Other files with metadata for debugging purposes etc. may also be pooped out.
+Now compilation of a .cpp file generally proceeds in two phases. The first phase is called 'preprocessing', and we generally say that this is carried out by the [#the preprocessor|preprocessor], although in actuality there is no separate program for the preprocessor, it's just a routine run by the compiler. After preprocessing, the compilation proper begins and an .obj file is pooped out. Other files with metadata for debugging purposes etc. may also be pooped out.
 == The Preprocessor ==

← Older revision		Revision as of 02:30, 1 August 2016
Line 5:		Line 5:

	Now compilation of a .cpp file generally proceeds in two phases. The first phase is called 'preprocessing', and we generally say that this is carried out by the 'preprocessor', although in actuality there is no separate program for the preprocessor, it's just a routine run by the compiler. After preprocessing, the compilation proper begins and an .obj file is pooped out. Other files with metadata for debugging purposes etc. may also be pooped out.		Now compilation of a .cpp file generally proceeds in two phases. The first phase is called 'preprocessing', and we generally say that this is carried out by the 'preprocessor', although in actuality there is no separate program for the preprocessor, it's just a routine run by the compiler. After preprocessing, the compilation proper begins and an .obj file is pooped out. Other files with metadata for debugging purposes etc. may also be pooped out.
		+
		+	== The Preprocessor ==
		+	The job of the preprocessor is to fuck around with the .cpp file before the compiler proper gets its fingers on it. This is done with macros and preprocessor directives. Preprocessor directives all start with the '#' character. For example, the <code>#include</code> directive takes another text file and inserts it into the current .cpp file. This is generally used to jam .h files into your .cpp file. Another directive is the <code>#define</code> direction, which creates a preprocessor macro. The result of running the preprocessor on a .cpp file, with all headers included and all macros expanded is called a ''translation unit'', and this is what is fed into the compiler proper.
		+
		+	== The Linker ==
		+	The linker has two main jobs: 1) take all the .obj files and jam them into one file and 2) link all the function call addresses to their destinations. You see, when the compiler is translating a function call into machine language, it won't know the address to jump to for the call if its in a different translation unit (.cpp file) because the compiler is only aware of the current translation unit it's working on, so the compiler leaves the address blank and the linker then fills that in afterwards.
		+
		+	Besides .obj files, the linker also accepts library (.lib) files as inputs. There's nothing special about .lib files, all they are is a bunch of .obj files jammed together for easy organization.
		+
		+	== Visual C++ Compiler ==
		+	The compiler in Visual Studio is named <code>cl.exe</code>, and the linker is named <code>link.exe</code> (<code>cl64.exe</code> and <code>link64.exe</code> for the 64-bit versions). If you're feeling especially masochistic you can try building some code from the command line. Also included is the assembler <code>ml.exe</code>. Proceed at your own peril ;)