Makefile File
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
Each subdirectory in a source code tree that includes a sources file also includes a makefile file. The following code example shows a directory structure and the placement of the makefile file.
\MyProj
Dirs
\Proj1
Dirs
Sources
Makefile
In an application development environment, such as Microsoft Visual Studio 2005, a makefile file contains all commands, macro definitions, and options that specify how to build a project.
By contrast, in Platform Builder, the sources files contain this type of information; the makefile file contains only a reference to the common makefile file, Makefile.def.
You should not edit the makefile file or alter Makefile.def. When creating your own projects in the OS tree, create a makefile file that simply includes makefile.def or copy an existing makefile file from another project. The following is a sample makefile file.
!include $(_MAKEENVROOT)\makefile.def
After Build.exe locates the dirs and sources files, it sets an internal environment variable. Nmake.exe uses this variable to append the Sources.cmn file to sources files in applicable subdirectories. For information about Sources.cmn, see Sources File.
Using the linking rules contained in Makefile.def, Nmake.exe compiles the source code specified in the sources files or it links object modules.
Nmake.exe uses Makefile.def to transform the current set of environment variables into calls to a compiler, linker, or other tool.
Nmake.exe uses other environment variables to determine the options that it passes to Shcl.exe.
For Windows Embedded CE: For example, if _TGTCPUFAMILY is set to SHx, Nmake.exe selects the Shcl.exe compiler.