Precompiled header

[DiDi]

What is the difference between automatic precompiled header, no precompiled header, create precompiled header and use precompiled header.

What does ...throught stdafx.h mean?

...and last but not least: What is a browse info file?

ÖÖÖÖÖ@OOOOOOOOOO00000000ooooooooooo°°°°°.... . . . . . . . . . .

[Dhwanit]

Automatic precompiled header: The first time an MFC VC program is compiled (generated by AppWizard) this option is used. The stdafx.h file is used for automatically generating a precompiled header.

No precompiled header: A precompiled header (.pch file) is not generated nor used when compiling other application components.

Create precompiled header: Generate the .pch file for use

Use precompiled header: Once the .pch has been created, use it for further compilation of other application components.

A PCH is a semi-compiled header file that reduces the time for compilation of other components that make up the application - like the other files (*.h, *.cpp) that are a part of the application. In AppWizard generated MFC application (projects) the main header file that is used for precompilation is the "stdafx.h" file (handed over from generation to generation of VC starting from 1.0). When you don't use a precompiled header, you'll notice that it takes longer for the entire project to compile (you can try it out and see for yourself).

A browser file is used to find symbols and functions in your projects. For example if you have a function called "FooBar" in one of your source code files but don't know which, you can use the browser information for finding it out. Apart from that if you want to see where else you've used "FooBar" in your application, you can again use the browser information to do the same.

Hope you find this helpful.


Cheers!
DP