RE: makefile by Umesh
Umesh
Fri Jun 08 08:49:04 CDT 2007
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.
But 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.
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.
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
!include $(_MAKEENVROOT)\makefile.def
Build utility invokes the correct tools with the appropriate options to
build your code. The Build utility is a wrapper around the Microsoft NMAKE
utility, so it handles issues like checking dependencies to ensure that the
correct files are rebuilt after a change.
for additional information to the Build utility, you could use Makefile.inc
This file allows you to add commands and dependencies to the makefile,
typically for pre- and post-processing of files related to the project
Regards
Umesh Jagga
"nihar" wrote:
> Hi all,
> In wince the makefile gets details from the sources filesto
> make the image.but is it possible that the make file can build
> without the help from sources file.if yes please explain a little
>
>
>
> Thanks
> Nihar
>
>