Precompiled headers - Revision history

Artojon: wikify

2006-07-10T11:10:57Z

wikify

Artojon: remove extra category

2006-07-08T15:34:38Z

remove extra category

Artojon: category fix

2006-07-08T15:07:28Z

category fix

Artojon: edited categories

2006-07-08T14:10:06Z

edited categories

Sethjackson at 20:47, 11 April 2006

2006-04-11T20:47:26Z

Sethjackson at 20:45, 11 April 2006

2006-04-11T20:45:58Z

Thomas at 15:22, 6 February 2006

2006-02-06T15:22:40Z

Mandrav: /* Marking a header for precompilation */

2005-12-14T19:14:28Z

Marking a header for precompilation

Mandrav: /* Using a precompiled header */

2005-12-14T19:14:02Z

Using a precompiled header

Mandrav: /* Marking a header for precompilation */

2005-12-14T19:13:15Z

Marking a header for precompilation

@@ Line 1: / Line 1: @@
 [[Category:User Documentation]]
-Are you tired of waiting until your project's compilation finishes?
+Using '''precompiled headers''' (or '''PCH''') speeds up the compilation of large projects (like Code::Blocks itself) by large amounts. This works by creating a header file which #includes all the rarely-changing header files for your project. Then the compiler is instructed to pre-compile this header file. This creates a new file which is now in a binary format that only the compiler understands. But, since it doesn't have to re-parse your header files for every source file that includes them, the process will now be considerably faster.
-If you answered yes above, then you 'd be happy to know that Code::Blocks, as of version 1.0rc2, supports precompiled headers for the GCC compiler.
+==Creating a precompiled header==
 To create a precompiled header for your project, just create a new header file.
 Say you named it "pch.h". Put the following in it:
@@ Line 46: / Line 38: @@
 </pre>
 Now this file is ready to be marked as PCH. To do this, find the file in the ProjectManager tree, right-click on it and select "Properties".
@@ Line 53: / Line 45: @@
 Click "Compile file" and make sure it's checked.
-Do <u>not</u> click "Link file".
 Also, set the priority weight to zero, to force it to be compiled before all other files (default priority is 50 - the lower this number, the higher the priority).
 Exit this dialog by clicking "OK".
 ==Using a precompiled header==
 You 're almost there. Only thing left is to actually include this file so that it can be used.
 There are two ways to do this.
@@ Line 67: / Line 62: @@
 -include "pch.h"
 </pre>
 The first line will emit a warning when building your project, if the PCH is _not_ used. It's nice to know this.
-The second line, does all the magic: it's like adding <tt>#include "pch.h"</tt> at the top of each of your source files, except you don't have to edit them ;)
 This doesn't work in all situations, but it's the quick way to add PCH in your project. Specifically, it won't work if the PCH is in the same directory as the project file. If that's the case, go to "Project->Properties" and set the PCH mode to "Generate PCH in a directory alongside the original file" (first option).

← Older revision		Revision as of 15:34, 8 July 2006
Line 1:		Line 1:
−	~~[[Category:Application Development]]~~
	[[Category:User Documentation]]		[[Category:User Documentation]]
	Are you tired of waiting until your project's compilation finishes?		Are you tired of waiting until your project's compilation finishes?

@@ Line 1: / Line 1: @@
 [[Category:Application Development]]
-[[Category:Development Documentation]]
+[[Category:User Documentation]]
 Are you tired of waiting until your project's compilation finishes?
 Are you using huge libraries for your project (like wxWidgets)?

@@ Line 1: / Line 1: @@
 [[Category:Application Development]]
-[[Category:Code::Blocks Development]]
+[[Category:Development Documentation]]
 Are you tired of waiting until your project's compilation finishes?
 Are you using huge libraries for your project (like wxWidgets)?

@@ Line 1: / Line 1: @@
-[[Ctaegory:Application Development]]
+[[Category:Application Development]]
 [[Category:Code::Blocks Development]]
 Are you tired of waiting until your project's compilation finishes?

← Older revision		Revision as of 15:22, 6 February 2006
Line 1:		Line 1:
		+	[[Category:Code::Blocks features]]
		+	[[Category:Development]]
	Are you tired of waiting until your project's compilation finishes?		Are you tired of waiting until your project's compilation finishes?
	Are you using huge libraries for your project (like wxWidgets)?		Are you using huge libraries for your project (like wxWidgets)?

@@ Line 60: / Line 60: @@
 There are two ways to do this.
-) Include it in every source file of your project (_not_ header files, only source files like *.cpp). This *must* be the very first C token in the file. In other words, put it really first. Only comments are harmless before it.
+# Include it in every source file of your project (_not_ header files, only source files like *.cpp). This *must* be the very first C token in the file. In other words, put it really first. Only comments are harmless before it.
+# Go to "Project->Build options" and add the following in "Compiler->Other options":
 <pre>
 -Winvalid-pch