The project facility allows you to create, modify, and select specifications for any number of builds. A default build specification is defined when you create your project. While a BSP is usually designed for one CPU, you can create build specifications for different image types and optimization levels, specifications for builds that include debugging information and builds that don't, and so on.

Each build specification consists of a set of options that define the VxWorks image type (for VxWorks and bootable application projects), makefile rules, macros, as well as compiler, assembler, and linker options.

The buttons at the bottom of the build property sheet allow you to create, edit, or delete makefile rules (default project entries cannot be deleted; only those created by a user can be deleted). When you click the New/Edit button The Create or Edit Rule dialog box appears (Figure 4-35). Once you have created or edited an entry, click OK. Note that the default is to invoke the rule before building the project (see the checkbox). If the default is not selected, the rule is only invoked if it is the rule currently selected for the build (with the drop-down list in the Rules page of the build property sheet). New rules are added to the projectName.wpj file and written to the makefile prior to a build.

Select the Macros tab of the build specification property sheet to view the makefile macros associated with the current project, build specification, and rules (Figure 4-36).

You can use the Macros page to modify the values of existing makefile macros, as well as to create new rules to be executed at the end of the build. Use the Delete button to delete a macro from the build. To add a macro, change the name and value of an existing macro, and click the Add/Set button. To change an existing macro, modify the value and click the Add/Set button.

The recommended way to link library (archive) files to your project is to add the libraries to the list defined by the LIBS macro.

The C/C++ compiler page of the build specification property sheet displays compiler options. You can edit the options displayed in the text box (Figure 4-37).

Select the assembler tab of the build specification property sheet to view assembler options. You can edit the options displayed in the text box (Figure 4-39).

Select the Link Order tab of the build specification property sheet to view module link order (Figure 4-40). You can change the link order using the Down and Up buttons to ensure that static C++ constructors and destructors are invoked in the correct order.

Select the linker tab of the build specification property sheet to view linker options. You can edit the options displayed in the text box (Figure 4-41).

To link an object file with a project, list the full path to the file. The recommended way to link library (archive) files is to add the libraries to the list defined by the LIBS macro (see Makefile Macros).

You can create new build specifications for a project with the Add New Build Specification window, which is displayed with the New Build option on the context menu. For example, one build specification can be created that includes debug information, and another that does not; specifications can be created for different image types, optimization levels, and so on. You can create a new build specification by copying from an existing specification, or by creating it as a default specification for a given toolchain (Figure 4-42).

Once you have created a new build specification, use the build specification property sheet to define it (see 4.5.1 Changing a Build Specification).

When you want to build your project, select the build specification from the Build Spec drop-down list (Figure 4-43).

Binaries produced by a build are created in the buildName subdirectory of your project directory.