Platform Settings: Build Options Tab (Windows CE 5.0)
This tab includes the following items.
- Buffer tracked events in RAM
- Select to buffer events tracked by OSCapture.exe in RAM.
- Enable CE Target Control Support
- Select to enable target control support during the boot process.
Selecting this also enables kernel independent transport layer (KITL).
- Enable Eboot Space in Memory
- Select to reserve memory space in the Config.bib file.
This allows the boot loader to save data that the OS can read at boot time.
- Enable Event Tracking during Boot
- Select to start the event-tracking subsystem.
- Enable Full Kernel Mode
- Select to run threads in kernel mode.
Note Enabling full kernel mode leaves the entire system vulnerable, but increases performance.
- Enable Kernel Debugger
- Select before building the run-time image to allow the debugger to connect and pass debugging information from the target device to the host device.
When Enable Kernel Debugger is selected, IMGNODEBUGGER is 0.
When cleared, IMGNODEBUGGER is 1.
- Enable KITL
- Select to enable KITL and to allow communication between the development workstation and the target device.
Clearing this also clears Enable CE Target Control Support if it is selected.
- Enable Profiling
- Select to enable Windows CE log kernel profiling in the run-time image.
This is the same as setting the IMGPROFILER or IMGCELOGENABLE environment variables to 1.
- Enable Ship Build
- Select to set the environment variable WINCESHIP to 1, which defines the compile time flag -DSHIP_BUILD.
This flag can be used to conditionally compile code.
If set, the OS doesn't output debug messages. If not set, the OS provides verbose debug messages to aid debugging.
This check box is displayed only in a release configuration, and is hidden in debug configurations.
- Flush tracked events to Release Directory
- Select to flush events to the release directory.
Selecting this also turns on event tracking.
- Run-time Image Can be Larger than 32 MB
- Select to enable a run-time image that requires 32 MB or more of RAM to successfully download to the target device after the run-time image is built.
- Use XCOPY instead of links to populate release directory
- Select to directly copy files to the release directory.
- Write Run-time Image to Flash Memory
- Select to allow the run-time image to be written to flash after download.
Send Feedback on this topic to the authors