OS Designs in a Source Code Control System
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
This topic provides information about best practices for managing Windows Embedded CE 6.0 OS designs in a source code control environment. In this environment, the fundamental goals for OS designs include the following items.
- Defining the settings for team-wide OS designs for the products that the team intends to ship.
Team-wide OS designs and settings assist in ensuring that the development process has a consistent baseline from which to begin developing the final product. - Defining the settings for emulation of these OS designs to enable application developers can develop applications without the targeted hardware.
Team-wide settings assist in ensuring that emulation of the OS design under development is consistent.
Files in an OS Design
Adding OS designs to a source control system is not necessarily a straightforward process, as there are files that are specific to the individual user, such as user preference files or build result files. These should not be placed under source code control.
The following table shows the files that you must put under source control in order to successfully manage an OS design called MyDesign in a source code control system.
| File | Description |
|---|---|
MyDesign\MyDesign.pbxml |
Required. The XML-based file that defines the OS design and its associated configurations. |
MyDesign\WINCE600 directory and subdirectories |
Required. Copies of the files from %_WINCEROOT%\Public\CEBASE. Parameter file customization for your OS design, contained in binary image builder (.bib) and registry (.reg) files. |
MyDesign\MyDesign.sln |
Optional. The file that defines the Microsoft Visual Studio 2005 solution. |
Do not add the following files to source code control because they are not useful in the source code control aspect of a team development environment.
- MyDesign\pbxml.user or MyDesign.suo
These are individual user preference files. - Reldir directory or subdirectories
These directories contain the files that result from the build process.
See Also
Concepts
Source Code Control: System Developers
Source Code Control: Getting Started