OS Design Configuration Properties (Compact 7)
3/12/2014
In Platform Builder, you can manage OS design configuration properties that affect your build. You can access the OS design configuration property pages in two ways: by using the shortcut menu and by using the menu bar.
To access the OS design configuration properties by using the shortcut menu
In Solution Explorer, right-click the OS design project and click Properties.
In the left pane of the Property Pages dialog box, select and expand the Configuration Properties menu item.
To access the OS design configuration properties by using the menu bar
In Solution Explorer, select the OS design project.
On the Project menu, click Properties.
In the left pane of the Property Pages dialog box, select and expand the Configuration Properties menu item.
There are six design configuration property pages.
General
You can set the name of the image and location of the Flat Release Directory on the General page. If you change either of these properties, you will have to re-run the Copy Files to Release Directory command.You can also select the build type: Debug, Release, or Checked.
Note
A debug image is useful for development because the image includes additional debug output. By using a debug image, you can perform full source-level debugging because compiler optimizations are turned off. For more information about the differences between debug, release, and checked builds, see The Build System.
- Locale
You can use the Locale page to set environment variables that are passed to the build localization tools during the build process. In in this manner, you can create an OS design for non-English languages.
- Build Options
You can set several environment variables on the Build Options page that affect how the image behaves, such as enabling the kernel debugger and profiling.
- Environment
You can set custom environment variables to influence the build on the Environment page. You typically use these variables together with custom build logic in a hardware platform or subproject. By default, none are set because this functionality is typically for advanced users.
- Custom Build Actions
You can set actions (typically batch files) to be called during the various build steps by using the Custom Build Actions page. Custom build actions are typically for advanced users and, by default, no actions are set.
- Subproject Image Settings
You can use the Subproject Image Settings page to include or exclude a subproject from the build or the final image. This page differs from the Subproject Properties page that you access by right-clicking a subproject in Solution Explorer.