Correct the token number for PcdDxePcdDatabaseTraverseEnabled
[mirror_edk2.git] / ReleaseNotes.txt
1 Intel(R) Platform Innovation Framework for EFI
2 EFI Development Kit II (EDK II)
3 Root Package 1.00
4 2006-07-06
6 Copyright (c) 2006, Intel Corporation
8 This document provides updates to documentation, along with a description on
9 how to install and build the EDK II.
11 Package Contents
12 ----------------
13 ReleaseNote.txt- These release notes for the package.
14 MdePkg - A package containing Industry Standard headers and libraries
15 Tools - A package containing Build Specific tools which are designed
16 to help the developer create and modify drivers and
17 libraries
18 EdkModulePkg - A package containing reference drivers
19 EdkFatBinPkg - A package containing binary DXE drivers for the Fat 32 file
20 system
21 EdkFatPkg - A package containing source DXE drivers for the Fat 32 file
22 system
23 EdkShellBinPkg - A package containing binary Shell applications and commands
24 EdkNt32Pkg - A package containing the NT32 Emulation platform reference
26 Note: MDE and MDK that appear in other documentation refer to the MdePkg and
27 Tools packages. These two packages are the minimum requirement for developing
28 EDK II Packages. It is also recommended that the top level files included
29 with the EDK be downloaded in conjunction with these two packages.
31 Note: Documents have the following filenames:
32 EDK II Module Development Environment Library Specification v0.50
33 (MDE_Library_Spec_0_50.rtf)
34 EDK II Build and Packaging Architecture Specification v0.50
35 (Build_Packaging_Spec_0_50.rtf)
36 EDK II Platform Configuration Database Infrastructure Description v0.51
37 (PCD_Infrastructure_0_51.rtf)
38 EDK II Module Surface Area v0.50
39 (Module_Surface_Area_0_50.rtf)
40 EDK II Module Development Environment (MDE) Package Specification v0.50
41 (MDE_Package_Spec_0_50.rtf)
42 EDK II C Coding Standards Specification v0.50
43 (C_Coding_Standards_Specification_ 0_50.rtf)
45 Pre-Requisites
46 --------------
47 The following list of tools must be installed on the development workstation
48 prior to using the Edk II.
50 Compiler Tool Chain
51 Microsoft* Visual Studio .NET 2003* (
52 or
53 A special GCC version 4.x or later ( See below.
55 Assembler Tool Chain
56 Microsoft Macro Assembler, version 6.15 or later
57 or
58 GNU binutils 2.16.1 or later
60 Java Development Kit ( Java 5.0 or later)
61 Sun* jdk-1.5.0_04 or later (
62 or
63 Bea Systems* jrockit-25.2.0-jdk1.5.0_03 or later (
65 Java Tools
66 Apache-ANT, version 1.6.5 or later (
67 Ant-contrib, version 1.0b2 or later
68 (
69 Saxon8, version 8.1.1
70 (
71 XMLBeans, version 2.1.0 (
72 DO NOT download the latest XMLBeans, version 2.2.0. It cannot work with
73 Saxon8, version 8.1.1.
75 Other Tools
76 TortoiseSVN version 1.3.3. (
78 Optional Tools
79 --------------
80 Compiler Tool Chains:
81 Intel C++ Compiler for Windows, ver. 9.0 or later (
82 Intel C Compiler for EFI Byte Code, ver. 1.2 or later
83 (
84 Microsoft Driver Development Kit, version 3790.1830 or later
85 (
86 Microsoft ACPI Source Language Assembler, Version 1.0.13NT or later
87 Intel ACPI Component Architecture, version 20060113
89 -----------------------
90 Notes On Required Tools (Source Control System)
91 -----------------------
92 The EDK II is being managed by the Subversion Source Control on
93 This software package provides speed, security, and additional features. The
94 recommended client is TortoiseSVN version 1.3.3.
95 (Available at
97 There are instructions for the use of Subversion Source Control on the
98 website, as part of the checkout procedures.
100 The URL of the EDK II repository is:
103 -----------------------
104 Notes On Documentation
105 -----------------------
106 The documents are being managed by the Subversion Source Control on
107 The document repository is "docs" and must be checked out
108 separately from the EDK II source tree. Refer to the checkout procedures on
109 the website for EDK II.
111 The URL of the document repository is:
115 -----------------------
116 Notes On Required Tools (With examples for Windows, OS X, and Linux)
117 -----------------------
118 Software Installation Order:
119 After installing the compiler tools and your Subversion client, the following
120 required tools should be installed in order:
121 Java JDK, Apache-Ant, ant-contrib, xmlbeans, saxon8
123 Java Development Kit:
125 The Java Environment Variable must be set before attempting to build.
126 For Sun JDK (see note below*):
127 set JAVA_HOME=c:\Java\jdk1.5.0_06 (Windows example)
128 export JAVA_HOME=/Library/Java/Home/ (OS X example)
129 export JAVA_HOME=/usr/lib/j2sdk1.5-sun/ (Linux example)
130 For Bea Systems:
131 set JAVA_HOME=c:\Java\jrockit-R26.0.0-jdk1.5.0_04
133 *When using the Sun JDK5.0
134 During installation, you should specify the install directory as C:\Java
135 instead of C:\Program Files\(or some other drive letter.) While installing
136 to this non-standard location is not required. In use, it seems to work
137 more reliably.
138 For the JDK, the install path would be C:\Java\jdk1.5.0_06
139 For the JRE, the install path would be C:\Java\jre1.5.0_06
140 Alternatively, you can specify C:\sunjavajdk and C:\sunjavajre.
142 NOTE: You cannot combine the location for the JDK and the JRE, as the JRE
143 install removes most of the binaries and libraries installed by the JDK
144 install.
146 Java Tools:
147 The Apache-ANT requires the ANT_HOME environment variable to be set before
148 attempting to build:
149 i.e. set ANT_HOME=c:\<full path to where ant was installed>
150 export ANT_HOME=~/ExternalTools/apache-ant (OS X and Linux example)
152 The ant-contrib.jar file should be installed in the %ANT_HOME%\lib
153 directory.
155 The XMLBeans, requires the XMLBEANS_HOME environment variable to be set
156 before attempting to build:
157 i.e. set XMLBEANS_HOME=C:\<full path to where xmlbeans was installed>
158 export XMLBEANS_HOME=~/ExternalTools/xmlbeans (OS X and Linux example)
160 The saxon8.jar file should be copied to the %XMLBEANS_HOME%\lib directory.
162 The Ant and XMLBean tools are required to be in the path.
163 MS system example:
164 set PATH=%PATH%;%ANT_HOME%\bin;%XMLBEANS_HOME%\bin
165 Linux/OS X bash shell example:
166 export PATH=$PATH:${ANT_HOME}/bin:${XMLBEANS_HOME}/bin
168 -------------------------------------------------------------------------------
169 Quick Start
170 -----------
171 For editing text files under Windows, use the Wordpad application. Notepad
172 does not handle UNIX style newline characters properly.
174 Copy the target.template file in the Tools/Conf directory to target.txt, which
175 must also be in the Tools/Conf directory.
177 Edit the text file, target.txt, located in the Tools/Conf directory. This
178 file contains options for setting the active platform and restricting the build.
179 The restictions are used to limit the build output by specifying build target(s),
180 tagname(s) and architecture(s) to less than the full set of possible options.
182 The ACTIVE_PLATFORM must be set unless the current working directory contains one
183 or more FPD files. All other options need not be set, however by unsetting these
184 options (by removing the line from the file, or leaving the Value empty) will
185 result in all available build possibilites when typing build. By default EDK II
186 can build a matrix of binaries, using different target types, tool chain tags and
187 architectures. Options to target.txt file are as follows:
190 Where Value is the WORKSPACE relative path and filename of a Framework Platform
191 Definition (FPD) File. Example:
193 ACTIVE_PLATFORM = MdePkg/MdePkg.fpd
196 Where Value is a list of one or more of the following: DEBUG, RELEASE or a User
197 Defined Target type, such as PERF. Example:
202 Where Value is a list of one or more supported Architectures: IA32, X64, IPF or
203 EBC. Example:
208 Where Value is the Filename of an alternate tools_def.txt file created by the
209 user. The alternate tools_def.txt files must be in the Tools/Conf directory.
210 These tool definitions are scoped to the WORKSPACE (location of the EDK
211 installation) and cannot be shared between WORKSPACES. (You can copy the files
212 from one workspace to another.) Example:
214 TOOL_CHAIN_CONF = alfred.txt
217 Where Value is a list of TagName entries as defined in the tools_def.txt file.
218 The TagName can be used to specify different versions of a compiler, i.e.,
219 gcc 4.0 and gcc 4.1 which will allow you to build binaries with both tool chains
220 during the same build - useful during testing of a new compiler tool chain, or
221 for changing compiler flags to check out performance with a different set of
222 flags than flags used for production. Example:
226 To clear a restriction, just remove any data after the equal sign. To clear
227 the TARGET_ARCH limitation that was set above, enter:
231 -----------
232 Copy the tools_def.template file in Tools/Conf to tools_def.txt in the same
233 directory.
235 Edit the tools definition file, tools_def.txt, also located in the Tools/Conf
236 directory. This file contains the names of the compiler tool chains and the
237 location of the compiler binaries. It has been pre-populated with the standard
238 location for the Microsoft tool chains and includes the standard location of
239 the Intel C Compiler for EFI Byte Code (EBC.) In addition, EDK II provides
240 support for Cygwin, Linux and OS X GCC compiler tool chains. A script has been
241 provided in the Tools/gcc directory as well as instructions in obtaining and
242 building a version of GCC that has been tested. The tools_def.txt file has
243 the GCC binary locations that are created using this script.
245 Both target.txt and tools_def.txt files are formatted as Property = Value,
246 which must appear on a single line. Spanning a Value entry over multiple
247 lines is not supported at this time. In the target.txt file, the Property is
248 a single, uppercase word with underscore characters. These Property names are
249 fixed by the build system. The tools_def.txt file's Property is an underscore
250 delimited coding, which supports some user defined values. The coding for
251 the Property is: TARGET_TAGNAME_ARCH_COMMAND_ATTR The Value, is either a
252 full path, full path and filename or a reserved word.
254 TARGET - DEBUG and RELEASE are predefined, however the user may define one or
255 more of their own TARGET types in this file.
257 TAGNAME - HOST, MSFT, GCC, INTC are predefined, however the user may define
258 one or more of their own TAGNAME keywords in this file.
260 ARCH - EDK II supports IA32, X64, IPF and EBC at this time.
262 COMMAND - Predefined command codes are listed in the tools_def.txt file, however
263 the user can specify additional command codes for their one, non-
264 standard tools.
266 ATTR - Predefined Attributes are listed in the tools_def.txt file.
268 NOTE: The TAGNAME: HOST is reserved and MUST be defined in order to build the
269 included Tiano tools from their C source files. These tools have been
270 built and tested using both Microsoft and GCC tool chains.
271 NOTE: The "*" symbol may be used as a wildcard character in most of these
272 fields, refer to the tools_def.txt and the "EDK II Build and Packaging
273 Architecture Specification" for more details.
276 -----------
277 Follow the instructions at to
278 checkout the entire EDK II source tree.
280 In a command window, change to the top level directory of the Edk II sources.
281 Set the WORKSPACE environment variable, e.g.:
283 c:\> set WORKSPACE=C:\MyWork\Edk2
285 To test your tool chain setup and to build the Supplied Tools, execute:
286 c:\MyWork\Edk2\> edksetup
288 On Unix systems you must source the file to load the correct
289 settings into your shell.
291 . # Note the dot.
293 (This command will be referred to as the setup command throughout the rest of
294 this document.)
295 NOTE: You should run the setup command at the start of every session.
296 This configures the environment to include the TianoTools and the
297 Java applications and libraries.
299 If you are confident that none of the tool tool sources have changed, and you
300 only want to set up the workspace environment you may execute:
301 c:\MyWork\Edk2\> edksetup skip
303 Once this is completed, you are ready to test the Build, by executing:
304 c:\MyWork\Edk2\> build
306 This command builds active platform specified in text file target.txt. If
307 active platform is not specified, go to sub-directory which contains FPD files and
308 type build. More information about active platform policy reference to specification
309 <<EDK II Build and Packaging Architecture Specification>>.
311 -------------------------
312 Individual Platform Builds
313 -------------------------
314 After running the setup command, you can build individual platforms.
315 In the command window,
316 1. Set active platform in target.txt, and type "build" in whatever directory;
317 2. or cd to the platform (FPD file) that you want to build, and just type:
318 c:\MyWork\Edk2\EdkNt32Pkg\> build
320 Note that active platform with the high priority to build, that means active
321 platform will be built even if exists FPD file under current directory. More
322 information about active platform policy reference to specification
323 <<EDK II Build and Packaging Architecture Specification>>.
325 Go to <full build path>\DEBUG\MSFT\IA32 and execute SecMain.exe
326 to run the Nt32 emulation platform under Microsoft Windows.
328 To exit the Nt32 emulation platform, you may type reset at the EFI Shell>
329 command prompt. Alternately, you may use the Graphical interface, Boot
330 Maintenance Manager screen's Reset System command.
332 ------------------------
333 Individual Module Builds
334 ------------------------
335 After running the setup command, you can build individual modules.
336 In the command window, cd to the module that you want to build, and just
337 type:
338 c:\MyWork\Edk2\MdePkg\Library\BaseLib\> build
340 Note active platform must be set for individual module build.
342 -------------------------------------------------------------------------------
343 A Word on Apache-ANT
344 --------------------
345 The Apache-ANT program is a build tool that uses XML-based project files.
346 Similar to Makefiles, these project files may contain multiple targets. Most
347 build.xml files in EDK II are auto-generated; any edits performed on the
348 build.xml files will be overwritten the next time build is executed.
350 Pre-defined targets in the build.xml file include:
351 all - This target builds binaries for defined architectures
352 clean - This target removes object files generated by commands
353 cleanall - This target removes all generated files and directories.
355 A Word on GCC tool chain
356 ------------------------
357 EDK II will not compile with a standard Linux gcc tool chain. While Linux
358 distributions are usually based on ELF, EDK II requires a version of gcc
359 that is configured to produce PE-COFF images. You will find a script in
360 edk2/Tools/gcc that will download, configure, compile, and install a gcc
361 4.X cross-compile tool chain for EDK II development. It has support for
362 the IA32 architecture. It can be built and run on Cygwin, Linux, and many
363 other POSIX compliant host operating environments. There are a few tools
364 that you will need on your host computer in order to compile the tool
365 chain. Among them are bash, gcc, gmake, curl (or wget).
367 -------------------------------------------------------------------------------
369 General Information:
370 ===============================================================
371 Mechanisms:
372 ----------
373 A brief overview:
375 A) Surface Area Package Description (SPD) file contains information about the
376 modules that the package contains, including the location of all MSA files, and
377 public library names and headers that might be provided by a module in the
378 package. Packages are defined by SPD files. (Found in the root of the Package
379 subdirectory (i.e. EdkNt32Pkg)) The SPD is further explained in the "EDK Build
380 and Packaging Architecture Specification" document.
382 B) Module Surface Area Definition (MSA) files. A description of a module's
383 surface area, with all module specific default flags and features specified.
384 Refer to the "Module Surface Area Architecture Specification" for additional
385 details. The MSA is further explained in the "EDK II Build Packaging Architecture
386 Specification" document.
388 C) Framework Platform Description (FPD) files. A description of a platform's
389 surface are, including a list of modules that are needed by the platform. To
390 support individual module builds, developers are not required to provide
391 information about specific flash devices, nor flash device layout. There are
392 specific sections in the FPD file that do control aspects of the build, such
393 as the Supported Architectures and Build Targets, as well as the tool flags
394 that are used to create the binary files. A valid platform file can specify
395 zero or more modules, so individual modules can be compiled within the context
396 of a platform (FPD) definition.
398 D) Platform Configuration Database (PCD). A platform database which contains a
399 variety of current platform settings or directives by which a driver or
400 application can interact with. The PCD is defined by the PCD_Protocol (This is
401 further explained in the "Platform Configuration Database Infrastructure
402 Description" document.
404 E) Library Class. A library class is a logical grouping of similar functions.
405 When developing components, the module surface area declares the class of
406 libraries that can be used by the component. The MSA and SPD files can specify
407 a recommended instance of the library that a platform integrator may select,
408 however this is only a recommendation. The PI may choose to select a different
409 library instance to be used during compilation/linking. All library type modules
410 must include header files in their distribution package, as well as their MSA
411 files. Components, on the other hand, need only provide an MSA and either source
412 or binary files when distributing packages. The Library Classes are further
413 explained in the "EDK II Build and Packaging Architecture Specification"
414 document.
416 =========================================================================
417 The common operations by developers of new modules are:
418 -------------------------------------------------------
420 1) How to manually create a new module in a package:
421 - The module source code must first be created in an appropriate directory
422 (under the package the module is to be a part of.)
423 - An MSA file must be created, spelling out all aspects of the module.
424 - The MSA must be added to the SPD for the package to include the module.
426 -----------------------------------------
427 2) Add/Remove module(s) to/from a package:
429 - Setup environment as Build
430 - Add a module to a package
431 * Generate the module SurfaceArea description file
432 * Add a new <Filename> element under <MsaFiles> into
433 <PackageDir>\<PackageName>.spd, using relative path to package
434 * Add a new <ModuleSA> entry under each <FrameworkModules> into
435 <PackageDir>\<PackageName>.fpd file if necessary.
437 - Remove a module from a package
438 * Comment out or remove corresponding <Filename> element under <MsaFiles>
439 from <PackageDir>\<PackageName>.spd
440 * Comment out or remove corresponding <ModuleSA> entry under each
441 <FrameworkModules> from <PackageDir>\<PackageName>.fpd if necessary.
443 -----------------------------------
444 3) How to manually create a package:
445 - Identify the modules that are to be members of the project.
446 - Identify the Variables and Guids required in and of the Package (including
447 consumption/production information).
448 - Create an SPD file defining these modules and calling out their MSA files.
449 - add a new <Filename> element under <PackageList> into
450 Tools\Conf\FrameworkDatabase.db, using the relative path to workspace.
452 --------------------------------------
453 4) Declare a new Protocol in a package:
454 - This release requires manual editing of the SPD file, adding the protocol
455 to the ProtocolDeclarations section of the file.
456 - Add the Protocol .h file to the Include\Protocol directory.
457 - Add an <Entry> to the <ProtocolDeclarations> element in the
458 <PackageName>.spd file
459 * Each line contains Protocol base name then the global variable name and
460 then the hex value of the Protocol GUID.
462 Example Protocol Entries (NOTE: The Guid entry is a single line in the SPD file):
463 <ProtocolDeclarations>
464 <Entry Name="Bds">
465 <C_Name>gEfiBdsArchProtocolGuid</C_Name>
466 <GuidValue>665E3FF6-46CC-11D4-9A38-0090273FC14D</GuidValue>
467 <HelpText/>
468 </Entry>
469 <Entry Name="Cpu">
470 <C_Name>gEfiCpuArchProtocolGuid</C_Name>
471 <GuidValue>26BACCB1-6F42-11D4-BCE7-0080C73C8881</GuidValue>
472 <HelpText/>
473 </Entry>
474 </ProtocolDeclarations>
476 ---------------------------------
477 5) Declare a new PPI in a package:
478 - This release requires manual editing of the SPD file
479 - Add the PPI .h file to the Include\Ppi directory.
480 - Add an <Entry> to the package <PpiDeclarations> element in the
481 <PackageName>.spd file
482 * Each line contains PPI base name then the global variable name and then
483 the hex value of the PPI GUID.
485 Example Ppi Entries (NOTE: The Guid entry is a single line in the SPD file):
486 <PpiDeclarations>
487 <Entry Name="BootInRecoveryMode">
488 <C_Name>gEfiPeiBootInRecoveryModePpiGuid</C_Name>
489 <GuidValue>17EE496A-D8E4-4B9A-94D1-CE8272300850</GuidValue>
490 <HelpText/>
491 </Entry>
492 <Entry Name="CpuIo">
493 <C_Name>gEfiPeiCpuIoPpiInServiceTableGuid</C_Name>
494 <GuidValue>E6AF1F7B-FC3F-46DA-A828-A3B457A44282</GuidValue>
495 <HelpText/>
496 </Entry>
497 </PpiDeclarations>
499 ----------------------------------
500 6) Declare a new GUID in a package:
501 - This release requires manual editing of the SPD file to include the new
502 Guid. This is identical to adding a ProtocolDeclaration or PpiDeclaration
503 element as described above.
505 ---------------------------------------
506 7) Declare a new PCD entry in a package:
507 - This release requires manual editing of the SPD file to include the new
508 PCD. New Pcd entries are added to the PcdDefinitions section of the
509 <PackageName>.spd file using the following example for the format:
510 NOTE: The hex <Token> value must be unique.
512 <PcdDeclarations>
513 <PcdEntry ItemType="FIXED_AT_BUILD">
514 <C_Name>PcdMaximumUnicodeStringLength</C_Name>
515 <Token>0x00000001</Token>
516 <TokenSpaceGuidCName>gEfiMdePkgTokenSpaceGuid</TokenSpaceGuidCName>
517 <DatumType>UINT32</DatumType>
518 <ValidUsage>FIXED_AT_BUILD</ValidUsage>
519 <DefaultValue>1000000</DefaultValue>
520 <HelpText>The maximum lengh for unicode string.</HelpText>
521 </PcdEntry>
522 </PcdDeclarations>
524 ------------------------------
525 8) Declare a new Library Class:
526 - This release requires manual editing of the SPD file to include the new
527 Library Class. New Library Class entries are added to the
528 LibraryClassDeclarations seection of the <PackageName>.spd file using
529 the following example for the format:
531 <LibraryClassDeclarations>
532 <LibraryClass Name="BaseLib">
533 <IncludeHeader>Include/Library/BaseLib.h</IncludeHeader>
534 <HelpText/>
535 </LibraryClass>
536 <LibraryClass Name="BaseMemoryLib">
537 <IncludeHeader>Include/Library/BaseMemoryLib.h</IncludeHeader>
538 <HelpText/>
539 </LibraryClass>
540 </LibraryClassDeclarations>
542 =======================================================
543 Notes:
544 ------
545 The EDK II represents significant changes in the structure of the EDK.
546 Therefore it is very difficult to isolate all of the changes of this version of
547 the EDK with the previous (EDK 1.0) version.
549 Of particular note:
551 1) EDK II contains new hardware feature support for the ICH SMBUS Libraries.
552 These libraries are provided to make Memory Reference Code (MRC) development
553 easier.
554 2) The MDE Libraries - The MDE libraries represent significant changes in source
555 (with only limited changes in functionality.) These new libraries conform
556 to the "MDE Library Specification".
557 3) The Fat Binary and the EDK Shell Binary Packages are functionally identical
558 to the EDK 1.0 version.
559 4) The EDK tools directory has been expanded to include more tools and more
560 tool functionality.
561 5) The EDK NT32 section has been ported to the new build process, but
562 functionally remains the same as the EDK 1.0 version.
563 6) The Application "HelloWorld" has been ported to EDK II as well.
565 =======================================================
566 Virus scanned by McAfee VirusScan Enterprise 8.0.0, Virus Definitions 4718, no
567 virus detected.