4.31 Selectively applying Precompiled Header (PCH) file processing

You can selectively include and exclude header files for PCH file processing, even if you are using automatic PCH file processing.

To do this, use the #pragma hdrstop directive to insert a manual header stop point in the primary source file. Insert it before the first token that does not belong to a preprocessing directive. This enables you to specify where the set of header files that is subject to precompilation ends. For example,

#include "xxx.h"
#include "yyy.h"
#pragma hdrstop
#include "zzz.h"

In this example, the PCH file includes the processing state for xxx.h and yyy.h but not for zzz.h. This is useful if you decide that the information following the #pragma hdrstop does not justify the creation of another PCH file.

Related concepts
4.24 Precompiled Header (PCH) files
4.25 Automatic Precompiled Header (PCH) file processing
4.26 Precompiled Header (PCH) file processing and the header stop point
4.27 Precompiled Header (PCH) file creation requirements
4.28 Compilation with multiple Precompiled Header (PCH) files
4.29 Obsolete Precompiled Header (PCH) files
4.30 Manually specifying the filename and location of a Precompiled Header (PCH) file
4.32 Suppressing Precompiled Header (PCH) file processing
4.33 Message output during Precompiled Header (PCH) processing
4.34 Performance issues with Precompiled Header (PCH) files
Related reference
10.85 #pragma hdrstop
10.90 #pragma no_pch
Non-ConfidentialPDF file icon PDF versionARM DUI0472J
Copyright © 2010-2013 ARM. All rights reserved.