Catalog Item Migration (Windows CE 5.0)

Article
09/14/2012

Information about displaying a Catalog item in the Catalog is contained in a .cec file. For information about creating a Catalog item, see How to Edit .cec Files Using a Text Editor.

Core Configuration

In earlier Windows CE versions, all OS designs were built using either the headless (HLBASE) or display-based (IABASE) core configurations. The choice of configuration affected the selection of available Catalog items in the Catalog. In Windows CE 5.0, there is only one core configuration, CEBASE. All OS designs are built using this configuration, facilitating selection and display of available Catalog items in the Catalog.

Platform Builder displays only Catalog items for the current Core OS, CEBASE, and filters any other Core OSes out of the Catalog view. So components marked as supporting HLBASE or IABASE are not displayed in the Catalog.
If a third party component indicates that it supports a specific Core OS in the .cec files, including CEBASE, this results in Platform Builder classifying the component as an OS feature instead of a BSP or a driver. Affected components will appear in the OS Features category instead of the BSP or Driver categories in the Catalog.

For troubleshooting information, see Troubleshooting: Third Party Catalog Components Do Not Appear Correctly After Migration.
The Catalog item (.cec) file format has changed, and .cec files are no longer used to contain dependency and build-specific information about associated Catalog items.

For more information about valid .cec file syntax, see Catalog Item Files.
BIBInfo blocks are deprecated; BuildMethod blocks are now only used to specify supported CPUs and provide links to source files, Help documentation (.chm), and Platform Builder project (.pbpxml) files.
- All build step actions in BuildMethod blocks are deprecated. This includes #COPY, #ENV, #BUILD, and #CUSTOM.
- Valid actions include #CHM, #SRCCODE and #CLONE_MODULE.
  
  #SRCCODE can be used to associate source code with a Catalog item, but the code will not be built.
For more information about valid BuildMethod block syntax, see Catalog Item Files.
In Windows CE 5.0, #COPY is no longer a valid build step. Instead, to copy files into the flat release directory, modify a makefile.inc file, and add or modify the sources macro definition WINCETARGETFILES in the sources file for the directory containing the files that you want to copy.

Navigate to the directory that contains the files that you want to copy, and then edit the sources file to include the macro definition WINCETARGETFILES, which specifies files that Build.exe will build after all other targets in the current directory are linked. For more information, see WINCETARGETFILES.

For example, if you want to copy files to an SDK called MySDK, set WINCETARGETFILES to CopySDK.

Then, in the same directory, create a Makefile.inc file that contains the following code.
```
CopySDK:
  if not EXIST $(_PROJECTSDKROOT)\Inc mkdir $(_PROJECTSDKROOT)\Inc 
        xcopy /I /D /Q *.h $(_PROJECTSDKROOT)\Inc > nul 
  if not EXIST $(_PROJECTSDKROOT)\lib mkdir $(_PROJECTSDKROOT)\lib 
  if not EXIST $(_PROJECTSDKROOT)\lib\$(_CPUINDPATH) mkdir 
$(_PROJECTSDKROOT)\lib\$(_CPUINDPATH) 
        xcopy /I /D /Q $(_TARGETPLATROOT)\lib\$(_CPUINDPATH)\$(TARGETNAME).* 
$(_PROJECTSDKROOT)\lib\$(_CPUINDPATH) > nul 
```

Catalog Item Migration (Windows CE 5.0)

Core Configuration

See Also

Additional resources