Use the INCLUDES macro to indicate the location of the headers to be included in your build. This macro should be invoked from within your Sources file.

This macro should be set to a list of the paths to be searched for header files during compilation. Separate the entries in this list by using a semicolon. Path names can be absolute, or relative to the directory in which the Sources file resides.

For example:


The INCLUDES macro is read by the Build utility. It examines the INCLUDES variable that you specify in your Sources file to determine the location of the header files that you are including in your source code so that it can build the dependency tree.

Paths that are specified in the INCLUDES macro will be searched before the default paths. The list of default paths is determined by the values of TARGETTYPE and DRIVERTYPE. Depending on the values of these macros, the default paths can include the values of any of the following macros: SDK_INC_PATH, DDK_INC_PATH, WDM_INC_PATH, CRT_INC_PATH, OAK_INC_PATH, or ATL_INC_PATH, MFC_INC_PATH.

You will usually use the INCLUDES macro in your Sources file to indicate to the Build utility the location of the headers to be included in your build. However, there are times when some header files may not exist (for example, if they are built as part of the build process). Such headers should be specified in the USER_INCLUDES macro.



Send comments about this topic to Microsoft

Build date: 5/3/2011