Source Code Configuration File Macros (Windows Embedded CE 6.0)

1/5/2010

The Microsoft Program Maintenance Utility (Nmake.exe), also known as the Nmake tool, and Build.exe use macro definitions in the dirs and sources files to build an OS design's source code to create a run-time image. These macro definitions use the following syntax.

Macroname= value

You can include white space to the left of the macro name and to the right of the equal sign. There can be no white space between the macro name and the equal sign. If the value has a backslash (\) as the last character on a line, the macro definition continues to the next line.

Given these rules, the following macro definitions are equivalent.

SOURCES= MyProj1.c MyProj1.h
SOURCES= MyProj1.c \
  MyProj1.h
SOURCES= \
  MyProj1.c \
  MyProj1.h

Macro names are not case-sensitive. Both Nmake.exe and Build.exe expand macro definitions. For example, Build.exe tries to expand the BBB macro in the following line.

AAA=  $(BBB)\Myproj

If BBB is not defined as a macro or environment variable, Build.exe defines the AAA macro as \Myproj.

See Also

Concepts

Source Code Configuration Files