Best Practices for Developing a Production-Quality OAL (Windows Embedded CE 6.0)

1/5/2010

The production-quality OAL best practices are recommendations for developing your own production-quality OAL and for customizing the production-quality OAL available in Windows Embedded CE.

• Reuse the BSP code provided in Windows Embedded CE.
  If the implementation in the %_WINCEROOT%\Platform\Common directory does not meet your needs, you can replace it by copying only the library that you need to replace.

• If you are creating a BSP that supports different images or variations, create a different BSP directory for each variation instead of creating just one BSP directory that uses environment variables to differentiate images.
  This approach minimizes confusion when you port your own hardware platform. It also increases the size of the Windows Embedded CE support library for the benefit of others. However, it might be preferable to use conditional codes to create different images if you have many files to copy into the BSP directory and if duplicate files would result from creating multiple BSP directories.

• Whenever possible, follow the layout and naming scheme used for the Windows Embedded CE OAL for your custom directories and files so that code can be located more easily.
  The hardware library and sample BSP code follow consistent coding guidelines, such as using common file and function-level comment headers that explain the function, its parameters, and error conditions.

• You can disable or enable the kernel independent transport layer (KITL) in run-time images that were built for retail devices, or for run-time images built for the emulator.

  Note

  An image with no KITL support does not support run-time application deployment.

  For more information, see BSP and SOC Directory Layout and BSP File-Naming Conventions.

See Also

Reference

KITL Reference for Production-Quality OAL

Concepts

Production-Quality OAL
Best Practices for Secure and Reliable OAL