Select the Appropriate Build Command (Compact 2013)

3/26/2014

To avoid stale binaries and prevent the rebuilding of unmodified code, select the most appropriate build command for your situation.

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

To determine which integrated development environment (IDE) build command to use, match your situation to the build commands shown in the following table.

Note

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

Command	IDE command(s)	When to use	Description
blddemo -q	Sysgen / Build <OS design> / Build Solution	When you create a new OS design in Platform Builder.	Runs the Sysgen phase on the blddemo command without the clean option. 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, and will still compile all of the needed binaries.
blddemo clean -q	Clean Sysgen / Rebuild <OS design> / Rebuild Solution	When you have changed Sysgen variables or catalog items.	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 performing a targeted build (as described in Create Targeted Builds). Important: 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.	Starts the build from the Build OS phase, but does not specify the clean option to clean the Sysgen output directory. This command is useful only 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. Important: 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.	Starts the build from the Build OS phase, and does a forced recompile of all files. 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).	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) (for example, changes to custom makefile rules) that require a recompile.	Starts the build from the Platform\common phase and does a forced recompile.

See Also

Concepts

Tuning the Build Process