Build Process

Windows XP Embedded Target Designer is used to build a configuration into a bootable run-time image. The order in which components are processed is dictated by their build order dependencies, if any. The order in which resources are processed is dictated by their build order number, when it is specified. The build process assembles all of the files and other data needed, and copies them to the appropriate directory structure and location. The build process also creates the registry hives and any other subsidiary files that might be required by the run-time image, such as Boot.ini. Build error messages are displayed in Windows XP Embedded Target Designer as they occur.

Once the build is complete, you can deploy the run-time image to your target device.

In This Section

• Defining Build Options
  Describes how to set default folders for extra files, run-time images, and build logs.
• Building a Run-Time Image
  Describes how to build a run-time image from a configuration.

Related Sections

• Windows XP Embedded Target Designer Guide
  Describes how to use Windows XP Embedded Target Designer to create, customize, and build a bootable run-time image.

See Also

See Deploy a Run-Time Image in Windows XP Embedded Help for a description of the process of deploying a run-time image to a variety of media types and the components and tools that are used for this purpose.

See Build Order Dependencies in Windows XP Embedded Help for a description of dependencies that require that one component be built before another during the run-time image build process.

Last updated on Wednesday, October 18, 2006

© 2006 Microsoft Corporation. All rights reserved.