Building and Downloading Migration (Windows CE 5.0)
In Microsoft Windows CE 5.0, the functionality for building and downloading a run-time image to a target device has changed from earlier versions of Platform Builder. If you are unfamiliar with Windows CE, it is recommended that you familiarize yourself with the content in the Tutorials.
Migrating from Windows CE .NET
For information about migrating an existing OS design to Windows CE 5.0, see How to Migrate a Windows CE .NET 4.2 OS Design to Windows CE 5.0.
Menu options related to builds have been updated. For more information, see Platform Builder Menu Migration.
The Build Selected Feature(s) functionality has been replaced with Targeted Builds. For more information, see Running a Targeted Build.
In Windows CE 5.0, there are no specific steps for migrating functionality from earlier versions of the user interface (UI) for kernel connectivity.
The main aspect of this functionality is the Target Device Connectivity Options dialog box, which is based on the new Core Connectivity functionality. For more information, see Core Connectivity Overview.
In Windows CE 5.0, the following download services and kernel transports are Core Connectivity-based:
- Emulator download service
- Ethernet download service
- Serial download service
- Emulator kernel transport
- Ethernet kernel transport
- Serial kernel transport
- USB kernel transport
Also, the USB kernel transport is new for Windows CE 5.0.
The underlying Core Connectivity infrastructure for these services is largely transparent to the user. Most UI settings for these services are the same as the UI settings for the same services for previous versions of Platform Builder.
For more information about these services and the associated UI, see Target Device Connectivity Options Dialog Box.
At the application level, application connectivity provided by Platform Manager behaves the same on the surface as application connectivity for previous versions of Platform Builder.
Windows CE 5.0 supports both Core Connectivity and Platform Manager. Core Connectivity is the replacement for Platform Manager, but you can still use Platform Manager in Windows CE 5.0.
In code, use the Core Connectivity API. Do not use the Platform Manager API except in code that does not need to be compatible with future releases of Windows CE.
Migrating from Windows CE 3.0
The Windows CE build environment tool (Wince.bat) interface and object structure has been updated with a simplified Wince.bat interface and object directory structure.
Microprocessor names now represent microprocessor architectures, and many environment variables have been updated.
The updates to the build environment are implemented in %_WINCEROOT%\Public\Common\Oak\Misc\Makefile.def.
The build environment is created with the microprocessor name, the hardware platform, and the OS design, as shown in the following example:
Wince.bat x86 CEBASE CEPC
For more information, see Windows CE Build Environment Tool.
Object files, libraries, and executables are in directories according to the microprocessor.
The %CEPBDir% environment variable is deprecated. Platform Builder still uses a default installation path unless you specify another location.
The %_TGTCPUFAMILY% environment replaces %_TGTCPUTYPE%. If you have a batch file, sources file, makefile file, Sources.cmn file, or Makefile.inc that includes a dependency on the %_TGTCPUTYPE% environment variable, update your code.
If you use paths with the %_TGTCPUTYPE%\%_TGTCPU%\%_TGTOS%\%WINCEDEBUG% format, use %_TGTCPU%\%WINCEDEBUG% instead.
This also applies for sources files.
See Also
Building and Downloading a Run-Time Image | Microprocessor Changes | Compiler Migration Issues
Last updated on Thursday, February 02, 2006
Send Feedback on this topic to the authors