The browser lets you view framework classes, such as the Microsoft Foundation Classes (MFC) for Windows and the PowerPlant classes for the Mac OS. If you want the browser to display these framework classes, you must include framework headers in such a way that the compiler sees them.

You should use precompiled headers to speed compilation time. However, if you simply use the precompiled headers directly, the compiler does not see the framework classes and does not generate information for the symbol database.

To resolve this problem, include a renamed copy of the source file that creates the precompiled headers in your project. These source files are named with extensions that identify precompiled headers, like .pch or .pch++. Alternatively, include as a subproject the project that creates the precompiled headers.

Including these files creates a project-specific precompiled header. CodeWarrior builds this precompiled header from within your project, exposing framework symbols to the compiler, which generates information for the browser database.

The reason you want to include a renamed copy is to avoid problems associated with multiple projects that use the same precompiled headers. When one project updates the headers, it will be marked as changed for all other projects, which then rebuild the precompiled headers. This rebuilding step defeats the purpose of the precompiled headers.