Creating a Sources File and Makefile File for an Application (Windows Embedded CE 6.0)

  • Article

1/5/2010

Before you can build an instrumented application for Call Profiler, add a sources file and a makefile file to the directory that contains the source code for your application.

The Windows Embedded CE Build tool (Build.exe), which builds the source code in a directory, uses the sources file to determine which C-language and Microsoft Visual C++ source files to compile, and what type of binary file to build.

For more information about Build.exe, see Build Tool. For more information about sources files, see Sources File.

Each directory that contains a sources file must also contain a makefile file. For more information about makefile files, see Makefile File.

Note

You can create a directory for the source code for your application in the directory for your OS design. For example, you can create a directory for the source code at %_WINCEROOT%\OSDesigns<OS design name>.

To create a sources file and a makefile file for your application

  1. In the directory that contains the source code for your application, create a file and name it sources, with a dot (.) for the file name extension.

    A sources file does not have a file name extension.

  2. In the sources file, insert the text from the following code example.

    TARGETLIBS=$(_PROJECTROOT)\cesysgen\sdk\lib\$(_TGTCPU)\$(WINCEDEBUG)\coredll.lib
TARGETNAME=<name of your application>
TARGETTYPE=PROGRAM
SOURCES=<file name including file name extension for the file that contains the source code for your application>
INCLUDES=$(_PROJECTROOT)\cesysgen\sdk\inc

    For more information about formatting, see Sources File.

  3. In the directory that contains the source code for your application, create a file and name it makefile, with a dot (.) for the file name extension.

    A makefile file does not have a file name extension.

  4. In the makefile file, insert the text from the following code example.

    !INCLUDE $(_MAKEENVROOT)\makefile.def

See Also

Tasks

How to Use Call Profiler to Find Performance Problems