Build Utility Limitations and Rules
There are a number of limitations and rules associated with the Build utility.
Only one DLL or library can be built in a given source directory. The equivalent of an import library is generated automatically when you build a DLL. The equivalent import library and export file are also generated.
If your DLL must link with other libraries, these libraries must be specified in your Sources file with a TARGETLIBS statement. (For a description of the proper "*" notation, see the TARGETLIBS page.)
The Build utility does not process NMAKE macros or conditional syntax. Consequently, the value of a Build utility macro in a Sources file must be textual; it cannot contain references to NMAKE macros.
Only files in the current directory, its parent directory, and the platform subdirectory can be listed in the SOURCES macro.
No blank spaces can appear in the file names or paths listed in the SOURCES macro. This includes the absolute path (or complete path) if only the relative path is specified.
No leading hyphens (-) can appear in the file names or paths listed in the SOURCES macro.
Build date: 5/3/2011