EDK II Build Specification
Search…
EDK II Build Specification
1.0.0
EDK II Build Specification
Tables
Figures
1 Introduction
2 Design Discussion
3 UEFI and PI Image Specification
4 EDK II Build Process Overview
5 Meta-Data File Specifications
6 Quick Start
6.1 Environment Variables
6.2 Build Scope
7 Build Environment
8 Pre-Build AutoGen Stage
9 Build or $(MAKE) Stage
10 Post-Build ImageGen Stage - FLASH
11 Post-Build ImageGen Stage - Other
12 Build Changes and Customizations
13 Build Reports
Appendix A Variables
Appendix B tools_def.txt
Appendix C target.txt
Appendix D build.exe command
Appendix E NT32 Platform Emulation
Appendix F Firmware Volume INF
Appendix G VS2005 Team Suite Performance
Appendix H Module Types
Appendix I VPD Tool
Appendix J Makefiles
Appendix K Third Party Tool Flags
Powered By GitBook
6 Quick Start
This chapter describes the build environment. Additional chapters describe how the build system parse files, creates C files and assembles binary images into PI compliant firmware images. The EDK II build system uses multiple threads during the build process. The maximum number of threads that will be spawned is controlled in the Conf/target.txt file. Typically, this value will be one more than the number of cores that are on the development workstation. Increasing the number beyond the N+1 value will not offer any performance benefit.
Note: Path and Filename elements within the Build Meta-Data files and command-line arguments are case-sensitive in order to support building on UNIX style operating systems.
A build is always performed within the context of a "platform" defined in a single workspace. Multiple platforms can be defined in any one workspace. While some developers will not be building actual platform firmware; the platform definition file (DSC) format is suitable for Option ROM and stand-alone application development, as well as flexible enough to create binary distribution code for individual modules as well as a full platform firmware file.
One set of EDK II build tools is required on a development system. The source code for these tools is written in either generic C or Python.
Refer to the TianoCore.org Getting Started with EDK II web page for additional information on setting up and using the EDK II build system.
Previous
5.3 target.txt File
Next
6.1 Environment Variables
Last modified 1yr ago
Copy link