### Prefix Files

In previous Carbide compilers, the prefix file was a distinct setting that told the compiler to include a source code file at the beginning of each source code file in a project’s build target, or include a precompiled header file into the project.

With this compiler release, the concept of prefixing files, #defines, and #pragmas has been extended.

To specify a prefix file, add an #include directive to this field, for example:

#include "Win32Headers.h"

To specify #defines or #pragmas, enter them here as you would in source code:

#define DEBUG_BUILD 1
#pragma warn_illtokenpasting off

When building precompiled headers, note the Include prefix text in precompiled headers setting. When enabled, the contents of the Prefix Text are used to generate the precompiled header. If your project generates a precompiled header in the same target that uses it, follow the form:

#if !__option(precompile)
#include "MyHeaders.mch"
#endif

to exclude the *.mch file when generating it.

NOTE #pragmas may affect aspects of parsing and type declaration while building a precompiled header, but these settings are not retained in the body of the precompiled header. Thus the prefix text is used for every file in the target.