Dirs and sources files in the WinCE BSP

1.Dirs file

About the dirs file, is to specify the path to compile, this earth people know. Just a brief introduction. There are three definitions as described above: Dirs,dirs_ce and Optional_dirs.

Dirs: is to specify the directory to compile.

Dirs_ce: The directory is compiled only if the source code under the directory is used for wince image files.

Optional_dirs: Specifies the directory to which you can choose to compile. For example: optional_dirs=proj1, if you want to compile the proj1 directory, you can set the build_options=proj1, and then run the build command.

As an example:

dirs= common \
            drivers \
            oal \
            bootloader

Indicates that the Common,drivers,oal and bootloader directories need to be compiled.

dirs=*

Represents the compilation of all current directories.

2.Sources file

In the wince BSP will see a lot of sources files, usually with the source code in the same directory, of course, is not absolute. These sources files are defined as macros that tell Build.exe how to compile and link when compiling the source code, tell Nmake.exe how to compile the source code, and what type of file to generate eventually.

Here is a specific description:

TARGETNAME: The name of the target file that was generated after the last compile, excluding the extension.

TargetType: The type of file that is generated. The specific values are as follows:

LIBRARY, a. lib file

Dynlink, a. dll file

program, an. exe file

ReleaseType: This macro sets the two environment variables Releasedir and Releaselibdir, which is to set the path for the compiled file to be stored. The specific values are as follows:

PLATFORM, generated files in platform\<bsp name>\<target>

Local, the generated file is under the current path

CUSTOM, the generated file is specified in the TargetPath location

MANAGED, generated files in%_projectroot%\oak\<target>\managed

OAK, SDK, DDK, generated files in%_projectroot%\oak\<target>

TargetPath: When the above Releasetype=custom, the macro specifies the path

Sourcelibs: Static link. The entity of the function is chained up to produce a copy

Targetlibs: Dynamic Link. The address of the function is chained and the library is loaded when the system executes

INCLUDES: Specifies the path to the additional header file to search for

SOURCES: Specifies the file to be compiled

Adefines: Specifies the parameters to be used by the assembler

Cdefines: Specifies the parameters to be used by the compiler

Ldefines: Specifies the parameters to be used by the connector

Rdefines: Specify parameters for Resource Compiler Rc.exe