EDK II Build Specification

DRAFT FOR REVIEW

Acknowledgements

Redistribution and use in source (original document form) and 'compiled' forms (converted to PDF, epub, HTML and other formats) with or without modification, are permitted provided that the following conditions are met:
  1. 1.
    Redistributions of source code (original document form) must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified.
  2. 2.
    Redistributions in compiled form (transformed to other DTDs, converted to PDF, epub, HTML and other formats) must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS DOCUMENTATION IS PROVIDED BY TIANOCORE PROJECT "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL TIANOCORE PROJECT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Copyright (c) 2008-2017, Intel Corporation. All rights reserved.

Revision History

Revision
Revision History
Date
1.0
Initial release.
February 2008
1.1
Update based on errata
August 2008
1.2
Updates based on enhancement requests
June 2009
1.21
Updates based on errata and enhancement requests
January 2010
Definitions in DSC file [defines] section are now global to both DSC and FDF files
Added language filters: RFC_LANGUAGES and ISO_LANGUAGES
Rule processing for file type lists is alphabetical, i.e., files are added in alphabetical order
Added warning for VFR file naming convention - cannot use a name that is also used for a C file
Use of the IDENTIFIER statement in tools_def.txt is optional
Whitespace characters are permitted in the meta-data files, so tools must handle them (use of token based processing is recommended)
Tools must support any number of FV_EXT_ENTRY_TYPE statements in an FDF file
The build tools must auto compute the ExtHeaderOffset in the FV Header.
The build tools must auto compute the ExtHeaderSize in the FV Ext Header based on the size of the FV Ext Header and all the FV Ext Header Entries.
The build tools must auto compute the ExtEntrySize field in the FV Ext Header Entry structure based on the size of the file specified by the FILE statement or the number of bytes in the byte array of the DATA statement. If the size is greater than 16-bits, the build should break.
Specified parsing priority rules for definitions and values
Added report generator syntax as part of the build
Add support for "Auto" alignment for PE32 and TE images
Add support for specifying block information for capsules
FeatureFlagExpression processing should allow C-style expression syntax and follow C rules for processing
Last modified 2yr ago