Define the image using OEMInput and feature manifest files

Learn how to create an OEMInput and feature manifest files to fully define the contents of your mobile image.

In this section

Topic	Description
OEMInput file contents	An OEMInput.xml file contains the required and optional elements used to define a mobile image. The OS uses this file to determine the applications processor, build type, UI languages, default region format, resolution, and other properties to include in the image that will be generated. This topic provides a full listing of the XML schema for the file.
Optional features for building mobile images	You can add optional features to images by including them under the Features element in the OEMInput XML file.
Feature manifest file contents	Feature manifest (FM) files are used to define specific types of image builds that contain different sets of optional packages. This topic describes the required and optional elements in a FM file.
Create a feature and include it in an image	This topic shows you how to create a feature and add it to an image.
Adding a driver to a test image	This topic shows you how to create a feature and add it to a test image.
Feature groupings and constraints	Feature groups and feature constraints allow additional logic to be added to the build system to support intelligent processing of the OEMInput XML.
Set device platform information	Learn about the prerequisites for building an image that can be flashed to a mobile device, including additional device platform information such as partner names, version numbers, and device names, before the image is finalized for retail devices.