¦ Default Locale Defines the default locale for the OS design. The default language is English (United States), which uses the default code page 437 (OEM-United States).
¦ Code Pages Specifies the ANSI and OEM code pages that will be available in the OS design.
¦ Localize The Build Instructs the build process to use localized string and image resources. Platform Builder performs the localization of the OS design during the make image step of the OS design build process. Localized resource files are integrated inside the binary files for the common components, through res2exe.
¦ Strict Localization Checking In The Build Causes the build process to fail if localization resources are missing, rather than just using the resources based on the default locale.
Build Options
Directly under the Locale node in the Property Pages dialog box, you can find the Build Options node, which enables you to control event tracking, debugging, and other build options for the active OS design, as illustrated in Figure 1-3.
Figure 1-3 Build Options property page
The Build Options property page enables you to configure the following options for the run-time image:
¦ Buffer Tracked Events In RAM Causes Platform Builder to include OSCapture.exe in the CE image. Also enables logging of operating system events tracked by OSCapture.exe in RAM so they can be flushed to a file and viewed later.
¦ Enable Eboot Space In Memory Enables the Ethernet boot loader (EBOOT) to pass data to the Windows Embedded CE OS at start time.
¦ Enable Event Tracking During Boot Enables CE event log data collection much earlier during the start process than it would normally be collected otherwise. If you activate this option, event tracking starts before most of the kernel and file system initialization is complete.
¦ Enable Hardware-Assisted Debugging Support This is required for some third- party hardware debugging tools (JTAG probes compliant with exdi2).
¦ Enable Kernel Debugger Enables the Windows Embedded CE debugger so you can step through the code in the run-time image. Kernel debugging requires KITL to communicate with Platform Builder at run time.
¦ Enable KITL Adds KITL to the run-time image. KITL is a useful debugging feature that enables developers to use the kernel debugger, interact with the remote device's file system, registry, and other components, as well as run code. You should not include KITL in the final build of the operating system, because it introduces overhead and wastes time during the start process trying to connect to a host computer.
¦ Enable Profiling Enables the kernel profiler in the run-time image, which you can use to collect and view timing and performance data. The kernel profiler is a useful tool for optimizing the performance of Windows Embedded CE on a target device.
¦ Flush Tracked Events To Release Directory Adds CeLogFlush.exe to the runtime image, which automatically flushes log data collected by OSCapture.exe to the Celog.clg file in the release directory on the development computer.
¦ Run-Time Image Can Be Larger Than 32 MB Enables you to build a larger-than-32- MB image. However, you should not use this option if you want to build an image larger than 64 MB. In this case, you must set an environment variable for the appropriate size (such as IMGRAM128).
¦ Use Xcopy Instead Of Links To Populate Release Directory Creates actual copies of the files by using xcopy rather than copylink. Copylink might only create hard links to the files rather than copying them, and it requires the NTFS file system on the development computer.
¦ Write Run-Time Image To Flash Memory Instructs EBOOT to write the run-time image to the flash memory of the target device.
Environment Options
The Property Pages dialog box provides an Environment option to configure environment variables that will be used during the build process. You can enable most features in Windows Embedded CE 6.0 R2 by using catalog components, but for some options you need to set a SYSGEN variable so that Platform Builder compiles the necessary code and includes it in the run-time image. Setting environment variables that influence the build process can be helpful when developing a BSP. Environment variables are accessible during the Windows Embedded CE build process from the command line. You can also use environment variables to specify flexible information in the sources, binary image builder (.bib), and registry (.reg) files.
If you can build a run-time image in the Debug configuration, but not in the Release configuration, display the Property Pages dialog box, select All Configurations from the Configuration list box, and then select the Environment option to set the environment variables for both Debug and Release to the same values.
Advanced OS Design Configurations
This section covers several advanced topics related to OS designs. Specifically, this section explains how to support multiple platforms with the same OS design and discusses the file locations and file types that an OS design typically includes.
Associating an OS Design with Multiple Platforms
When creating a new OS design project by using the OS Design Wizard, you can select one or more BSPs on the Board Support Packages wizard page. By associating an OS design with multiple BSPs, you can generate separate run-time images with identical content for multiple platforms. This is particularly useful in projects that include multiple development teams, especially if the final target hardware is currently not available. For example, you can generate a run-time image for an emulator-based platform so that the application development team can start before the final hardware is available. In terms of OS functionality, the application development team can use the application programming interfaces (APIs) before the final target platform is available. The APIs will be included in the final target because the two run-time images share the same set of components and configuration settings.
You can also add support for multiple platforms to an OS design after the initial creation. All you need to do is select the corresponding check boxes under BSP in the Catalog Items View of Solution Explorer. Selecting a BSP automatically adds the additional platform to the configuration for Release and Debug. You can then switch
