1.1 Overview
EDK II tools use INI-style text-based files to describe components, platforms and firmware volumes. The EDK II Build Infrastructure supports generation of binary images compliant with Unified EFI Forum (UEFI) specifications UEFI and Platform Initialization (PI).
The EDK II build processes, defined in the EDK II Build Specification, use separate steps to create EFI images. EDK Build Tools are included as part of the EDK II compatibility package. In order to use EDK II Modules or the EDK II Build Tools, EDK II DSC and FDF files must be used.
The EDK II FDF file is used in conjunction with an EDK II DSC file to generate bootable images, option ROM images, and update capsules for bootable images that comply with the UEFI specifications listed above.
The FDF file describes the content and layout of binary images that are either a boot image or PCI Option ROMs.
This document describes the format of EDK II FDF files that are required for building binary images for an EDK II platform. The goals are:
Compatibility - No compatibility with EDK FDF files exists in format or tools.
Simplified platform build and configuration - The FDF files simplify the process of adding EDK components and EDK II modules to a firmware volume on any given platform.
The EDK build tools are provided as part of the EdkCompatibilityPkg which is included in EDK II.
Table 1 shows the FDF compatibility between platform, module and component builds.
Table 1 EDK Build Infrastructure Support Matrix
EDK FDF | EDK II FDF | EDK DSC | EDK II DSC | |
---|---|---|---|---|
EDK Build Tools | YES | NO | YES | NO |
EDK II Build Tools | NO | YES | NO | YES |