NTTARGETFILE0

  • Article

You can define the NTTARGETFILE0, NTTARGETFILE1, or NTTARGETFILE2, or NTTARGETFILES macros to cause Makefile.def to include Makefile.inc immediately after it specifies the top level targets (all, clean, and loc) and their dependencies.

The Makefile.def file expands NTTARGETFILE0 as the first dependent for the all target, and NTTARGETFILES as the last dependent for the all target. Use this macro to specify additional targets and dependencies that do not fit the general case covered by Makefile.def.

NTTARGETFILE0=

The fact that NTTARGETFILE0 exists, even if it is defined and empty, causes the Build utility to open Makefile.inc in the same subdirectory as the Sources file.

If you set NTTARGETFILE0 to equal a file name, the Build utility will not only include Makefile.inc, but will also build the executable program that the macro defines. Therefore, if you set:

NTTARGETFILE0=myfile.a

the Build utility builds myfile*.a* as part of Pass 0.

If you do not set NTTARGETFILE0, the Build utility locates the specified subdirectory on Pass0, includes the Makefile.inc in that subdirectory, and follows any default rules that this file contains.

See Also

NTTARGETFILE1, NTTARGETFILE2, NTTARGETFILES, Pass 0

 

 

Send comments about this topic to Microsoft

Build date: 5/3/2011