Best Practices for Developing a Production-Quality OAL (Windows CE 5.0)
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 CE 5.0.
Reuse the BSP code provided in Windows CE 5.0.
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 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 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.
For more information, see BSP and CSP Directory Layout and BSP File-Naming Conventions.
See Also
Best Practices for Secure and Reliable OAL | Production-Quality OAL
Send Feedback on this topic to the authors