Share via


Select the Appropriate Build Command (Compact 7)

3/12/2014

Select the most appropriate build command for your situation to avoid stale binaries and prevent rebuilding unmodified code.

The build system examines Sysgen variables (variables whose names begin with "SYSGEN_") to determine what components and features to include in the OS run-time image. Platform Builder sets Sysgen variables when you add a catalog item to your OS design. When the Sysgen variables change, we recommend that you use the clean option on your blddemo command to force the output binaries to be generated again. For more information on blddemo and its options, see Build Demo Tool (Blddemo.bat).

You can determine which integrated development environment (IDE) build command to use by matching your situation to the build commands shown in the following table.

Note

All of the IDE commands are on the Build menu or on the Advanced Build Commands submenu of the Build menu.

Command IDE command(s) When to use What it does

blddemo -q

Sysgen / Build <OS design> / Build Solution

When you create a new OS design in Platform Builder.

This command runs the Sysgen phase without the clean option on the blddemo command. If you have changed Sysgen variables or catalog items, you must instead use blddemo clean -q to avoid stale binaries. If you have not changed Sysgen variables or catalog items, blddemo -qbsp will be faster while still compiling all of the needed binaries.

blddemo clean -q

Clean Sysgen / Rebuild <OS design> / Rebuild Solution

When you have changed Sysgen variables or catalog items.

This command cleans the Sysgen output directory and then runs a build starting from the Sysgen phase.

blddemo

Build and Sysgen

When you have modified public code and have not changed Sysgen variables or catalog items, but are not doing a targeted build (as described in Create Targeted Builds).

JJ200376.note(en-us,WinEmbedded.70).gifImportant:
We do not recommend the modification of public code, nor do we provide support for this practice. Public code modification examples are intended for an expert audience only.

This command starts the build from the Build OS phase but does not specify the clean option to clean the Sysgen output directory. This is only useful when you have modified public code.

blddemo clean cleanplat -c

Rebuild and Clean Sysgen

When you have modified public code and have also changed Sysgen variables.

JJ200376.note(en-us,WinEmbedded.70).gifImportant:
We do not recommend the modification of public code, nor do we provide support for this practice. Public code modification examples are intended for an expert audience only.

This command starts the build from the Build OS phase and does a forced recompile of all files. It also cleans the Sysgen output directory.

blddemo -qbsp

Build Current BSP and Subprojects

When you have not changed Sysgen variables or catalog items but have changed files or code in Platform\common or Platform\$(_TGTPLAT).

This command starts the build from the Platform\common phase but does not do a forced recompile.

blddemo -c -qbsp

Rebuild Current BSP and Subprojects

When you have not changed Sysgen variables or catalog items but you have made changes in Platform\common or Platform\$(_TGTPLAT) that require a recompile (for example, changes to custom makefile rules).

This command starts the build from the Platform\common phase and does a forced recompile.

See Also

Concepts

Improve The Build Process