[mirror_edk2.git] / ReleaseNotes.txt
aa0bf4f4 1Intel(R) Platform Innovation Framework for EFI\r
2EFI Development Kit 2.0 (EDK 2.0) \r
3Alpha Release\r
6Copyright (c) 2006, Intel Corporation\r
8This document provides updates to documentation, along with a description on \r
9how to install and build the Edk 2.0.\r
11Package Contents\r
13 ReleaseNote.txt- These release notes for the package.\r
14 MdePkg - A package containing Industry Standard headers and libraries\r
15 Tools - A package containing Build Specific tools which are designed\r
16 to help the developer create and modify drivers and\r
17 libraries\r
18 EdkModulePkg - A package containing reference drivers\r
19 EdkFatBinPkg - A package containing binary DXE drivers for the Fat 32 file\r
20 system\r
21 EdkShellBinPkg - A package containing binary Shell applications and commands\r
22 EdkNt32Pkg - A package containing the NT32 Emulation platform reference\r
24Note: MDE and MDK that appear in other documentation refer to the MdePkg and\r
25Tools packages. These two packages are the minimum requirement for developing\r
26EDK 2.0 Packages. It is also recommended that the top level files included\r
27with the EDK be downloaded in conjunction with these two packages.\r
29Note: Documents have the following filenames:\r
30 EDK 2.0 Module Development Environment Library Specification v0.50 \r
31 (MDE_Library_Spec_0_50.rtf)\r
32 EDK 2.0 Build and Packaging Architecture Specification v0.50\r
33 (Build_Packaging_Spec_0_50.rtf)\r
34 EDK 2.0 Platform Configuration Database Infrastructure Description v0.51\r
35 (PCD_Infrastructure_0_51.rtf)\r
36 EDK 2.0 Module Surface Area v0.50\r
37 (Module_Surface_Area_0_50.rtf)\r
38 EDK 2.0 Module Development Environment (MDE) Package Specification v0.50\r
39 (MDE_Package_Spec_0_50.rtf)\r
40 EDK 2.0 C Coding Standards Specification v0.50\r
41 (C_Coding_Standards_Specification_ 0_50.rtf)\r
45The following list of tools must be installed on the development workstation\r
46prior to using the Edk 2.0.\r
48Compiler Tool Chain\r
49 Microsoft* Visual Studio .NET 2003* (\r
50 or\r
43475442 51 A special GCC version 4.x or later ( See below.\r
aa0bf4f4 52\r
53Assembler Tool Chain\r
54 Microsoft Macro Assembler, version 6.15 or later\r
55 or\r
8fb9e6b8 56 GNU binutils 2.16.1 or later\r
aa0bf4f4 57\r
58Java Development Kit ( Java 5.0 or later)\r
59 Sun* jdk-1.5.0_04 or later (\r
60 or\r
61 Bea Systems* jrockit-25.2.0-jdk1.5.0_03 or later (\r
63Java Tools\r
64 Apache-ANT, version 1.6.5 or later (\r
50518883 65 Ant-contrib, version 1.0b2 or later\r
66 (\r
aa0bf4f4 67 Saxon8, version 8.1.1\r
68 (\r
69 XMLBeans, version 2.1.0 or later ( \r
71Other Tools\r
72 TortoiseSVN version 1.3.3. (\r
74Optional Tools\r
76Compiler Tool Chains:\r
50518883 77 Intel C++ Compiler for Windows, ver. 9.0 or later (\r
8fb9e6b8 78 Intel C Compiler for EFI Byte Code, ver. 1.2 or later \r
79 (\r
aa0bf4f4 80 Microsoft Driver Development Kit, version 3790.1830 or later\r
8fb9e6b8 81 (\r
aa0bf4f4 82 Microsoft ACPI Source Language Assembler, Version 1.0.13NT or later\r
83 Intel ACPI Component Architecture, version 20060113\r
86Notes On Required Tools (Source Control System)\r
88The EDK 2.0 is being managed by the Subversion Source Control on\r
89This software package provides speed, security, and additional features. The\r
90recommended client is TortoiseSVN version 1.3.3. \r
91 (Available at\r
93There are instructions for the use of Subversion Source Control on the\r website, as part of the checkout procedures.\r
96The URL of the EDK 2.0 repository is:\r
100Notes On Documentation\r
102The documents are being managed by the Subversion Source Control on\r The document repository is "docs" and must be checked out\r
104separately from the EDK 2.0 source tree. Refer to the checkout procedures on\r
105the website for EDK 2.0.\r
107The URL of the document repository is:\r
112Notes On Required Tools (MS Windows environment example)\r
114Software Installation Order:\r
115 After installing the compiler tools and your Subversion client, the following\r
116 required tools should be installed in order: \r
117 Java JDK, Apache-Ant, ant-contrib, xmlbeans, saxon8\r
119Java Development Kit:\r
120 \r
121 The Java Environment Variable must be set before attempting to build.\r
122 i.e. For Sun JDK (see note below*):\r
123 set JAVA_HOME=c:\ Java\jdk1.5.0_06 \r
124 i.e. For Bea Systems:\r
125 set JAVA_HOME=c:\Program Files\Java\jrockit-R26.0.0-jdk1.5.0_04\r
126 \r
127 *When using the Sun JDK5.0\r
128 During installation, you should specify the install directory as C:\Java\r
129 instead of C:\Program Files\(or some other drive letter.) While installing\r
130 to this non-standard location is not required. In use, it seems to work \r
131 more reliably. \r
132 For the JDK, the install path would be C:\Java\jdk1.5.0_06\r
133 For the JRE, the install path would be C:\Java\jre1.5.0_06\r
134 Alternatively, you can specify C:\sunjavajdk and C:\sunjavajre.\r
01d2ed5e 135\r
aa0bf4f4 136 NOTE: You cannot combine the location for the JDK and the JRE, as the JRE\r
137 install removes most of the binaries and libraries installed by the JDK\r
138 install.\r
140Java Tools:\r
141 The Apache-ANT requires the ANT_HOME environment variable to be set before\r
142 attempting to build:\r
01d2ed5e 143 i.e. set ANT_HOME=c:\<full path to where ant was installed>\r
aa0bf4f4 144\r
145 The ant-contrib.jar file should be installed in the %ANT_HOME%\lib \r
146 directory.\r
148 The XMLBeans, requires the XMLBEANS_HOME environment variable to be set\r
149 before attempting to build:\r
01d2ed5e 150 i.e. set XMLBEANS_HOME=C:\<full path to where xmlbeans was installed>\r
aa0bf4f4 151\r
152 The saxon8.jar file should be copied to the %XMLBEANS_HOME%\lib directory.\r
154 The Ant and XMLBean tools are required to be in the path.\r
155 MS system example:\r
156 set PATH=%PATH%;%ANT_HOME%\bin;%XMLBEANS_HOME%\bin\r
157 Linux/OS X bash shell example:\r
158 export PATH=$PATH:${ANT_HOME}/bin:${XMLBEANS_HOME}/bin\r
159 \r
161Quick Start\r
54a1ec66 163Edit the text file, msft_tools_def.txt, located in the Tools/Conf directory.\r
164This file contains the names of the compiler tool chains and the location of\r
165the compiler binaries. It has been pre-populated with the standard location\r
166for the Microsoft tool chains and includes the standard location of the Intel C\r
aa0bf4f4 167Compiler for EFI Byte Code (EBC)\r
168 \r
169Follow the instructions at to\r
170checkout the entire EDK 2.0 source tree.\r
172In a command window, change to the top level directory of the Edk 2.0 sources.\r
173 Set the WORKSPACE environment variable, e.g.:\r
175 c:\> set WORKSPACE=C:\MyWork\Edk2.0\r
177To test your tool chain setup and to build the Supplied Tools, execute:\r
178 c:\MyWork\Edk2.0\> edksetup\r
180(This command will be referred to as the setup command throughout the rest of\r
181this document.)\r
182 NOTE: You should run the setup command at the start of every session.\r
183 This configures the environment to include the TianoTools and the\r
184 Java applications and libraries.\r
186Once this is completed, you are ready to test the Build, by executing:\r
187 c:\MyWork\Edk2.0\> ant\r
189This command builds all of the packages, including the NT32 reference platform.\r
90f7b6a8 191------------------------------------\r
192Build Architectures other than IA32.\r
195By default, we are set up to build the ia32 architecture. If you would like to\r
196build for IPF, x64 and EBC, please copy MdePkg/MdePkg-All-Arch.fpd to\r
197MdePkg/MdePkg.fpd. For EdkModulePkg, copy EdkModulePkg-All-Archs.fpd to\r
198EdkModulePkg.fpd. Note, you may also add only the architecture you want from\r
199the -All-Archs files to the main fpd file. This is preferred if you do not have\r
200all the compilers installed.\r
202Optionally, you may modify the path to the compiler in\r
203Tools/Conf/msft_tools_def.txt. The flags for the ARCH tool chain are set in the\r
204file names by Tools/Conf/VENDOR_tools.txt, where VENDOR is set in\r
207For example, if IPF_VENDOR = WINDDK, then the flags for the IPF DDK compiler\r
208will be specified in Tools/Conf/winddk_tools.txt.\r
aa0bf4f4 210-------------------------\r
211Individual Package Builds\r
213After running the setup command, you can build individual packages.\r
214 In the command window, cd to the package that you want to build, and just\r
215 type:\r
216 c:\MyWork\Edk2.0\EdkNt32Pkg\> ant\r
218The EdkNt32Pkg has a special target; "run" that will execute the Nt32 emulation\r
219platform under Microsoft Windows.\r
03fed93e 221To exit the Nt32 emulation platform, you may type reset at the EFI Shell>\r
222command prompt. Alternately, you may use the Graphical interface, Boot\r
223Maintenance Manager screen's Reset System command.\r
aa0bf4f4 225------------------------\r
226Individual Module Builds\r
228After running the setup command, you can build individual modules.\r
229 In the command window, cd to the module that you want to build, and just\r
230 type:\r
231 c:\MyWork\Edk2.0\MdePkg\Library\BaseLib\> ant\r
234A Word on Apache-ANT\r
236The Apache-ANT program is a build tool that uses XML-based project files.\r
237Similar to Makefiles, these project files may contain multiple targets. Most\r
238build.xml files in Edk2.0 are auto-generated; any edits performed on the\r
239build.xml files will be overwritten the next time ant is executed.\r
241Pre-defined targets in the build.xml files include:\r
242 all - This target builds binaries for defined architectures\r
243 clean - This target removes object files generated by commands\r
244 cleanall - This target removes all generated files and directories.\r
246A Word on GCC tool chain\r
43475442 248EDK2 will not compile with a standard Linux gcc tool chain. While Linux\r
249distributions are usually based on ELF, EDK2 requires a version of gcc that is\r
250configured to produce PE-COFF images. You will find a script in edk2/Tools/gcc\r
251that will download, configure, compile, and install a gcc 4.X cross-compile\r
252tool chain for EDK2 development. It has support for the ia32 architecture. It\r
253can be built and run on Cygwin, Linux, and many other POSIX compliant host\r
254operating environments. There are a few tools that you will need on your host\r
255computer in order to compile the tool chain. Among them are bash, gcc, gmake,\r
256curl (or wget).\r
aa0bf4f4 257\r
260General Information:\r
261=============================================================== \r
8fb9e6b8 264A brief overview:\r
aa0bf4f4 265\r
266A) Surface Area Package Description (SPD) file contains information about the\r
267modules that the package contains, including the location of all MSA files, and\r
268public library names and headers that might be provided by a module in the\r
269package. Packages are defined by SPD files. (Found in the root of the Package\r
270subdirectory (i.e. EdkNt32Pkg)) The SPD is further explained in the "Build \r
271Packaging Specification" document.\r
272 \r
273B) Module Surface Area Definition (MSA) files. A description of a module's \r
274surface area, with all module specific default flags and features specified.\r
275Refer to the "Module Surface Area Architecture Specification" for additional\r
276details. The MSA is further explained in the "Build Packaging Specification"\r
278 \r
279C) Module Build Description (MDB). The "as-built" definition file that contains\r
280only the changes to the default flags defined in the MSA. The MSA and MDB are\r
281further explained in the "Build Packaging Specification" document.\r
283D) Platform Configuration Database (PCD). A platform database which contains a\r
284variety of current platform settings or directives by which a driver or\r
285application can interact with. The PCD is defined by the PCD_Protocol (This is\r
286further explained in the "Platform Configuration Database Infrastructure \r
287Description" document.\r
289E) Library Class. A library class is a logical grouping of similar functions.\r
290When developing components, the module surface area declares the class of\r
291libraries that can be used by the component. The MBD file specifies the\r
292instance(s) of the library that will be used during compilation/linking. All\r
293library type modules must include header files in their distribution package,\r
294as well as their surface area and module build description files. Components,\r
295on the other hand, need only provide the binary and build description files\r
296when distributing BINARY packages. The Library Classes are further explained\r
297in the "Build Packaging Specification" document.\r
300The common operations by developers of new modules are:\r
3031) How to manually create a new module in a package:\r
304 - The module source code must first be created in an appropriate directory\r
305 (under the package the module is to be a part of.) \r
306 - An MSA file must be created, spelling out all aspects of the module.\r
307 - The MSA must be added to the SPD for the package to include the module.\r
3102) Add/Remove module(s) to/from a package:\r
312 - Setup environment as Build\r
313 - Add a module to a package\r
314 * Generate the module SurfaceArea description file and build description\r
315 file\r
316 * Run GenBuildFile.bat under <PackageDir> to generate an entrance\r
317 build.xml for the module\r
318 * Add a new <MsaFile> element under <MsaFiles> into\r
319 <PackageDir>\<PackageName>.spd, using relative path to package\r
320 * Add a new <ModuleSA> entry under each <TianoImage> into\r
321 <PackageDir>\<PackageName>.fpd file\r
323 - Remove a module from a package\r
324 * Comment out or remove corresponding <MsaFile> element under <MsaFiles>\r
325 from <PackageDir>\<PackageName>.spd\r
326 * Comment out or remove corresponding <ModuleSA> entry under each\r
327 <TianoImage> from <PackageDir>\<PackageName>.fpd\r
3303) How to manually create a package:\r
331 - Identify the modules that are to be members of the project.\r
332 - Identify the Variables and Guids required in and of the Package (including\r
333 consumption/production information).\r
334 - Create an SPD file defining these modules and calling out their MSA files.\r
3374) Declare a new Protocol in a package: \r
338 - This release requires manual editing of the SPD file, adding the protocol\r
339 to the ProtocolDeclarations section of the file. \r
340 - Add the Protocol .h file to the Include\Protocol directory.\r
64fcaead 341 - Add an <Entry> to the <ProtocolDeclarations> element in the \r
342 <PackageName>.spd file\r
aa0bf4f4 343 * Each line contains Protocol base name then the global variable name and\r
344 then the hex value of the Protocol GUID.\r
64fcaead 346Example Protocol Entries (NOTE: The Guid entry is a single line in the SPD file):\r
348 <Entry Name="UnicodeCollation">\r
349 <C_Name>gEfiUnicodeCollationProtocolGuid</C_Name>\r
350 <Guid>{ 0x1d85cd7f, 0xf43d, 0x11d2, 0x9a, 0xc, 0x0, 0x90, 0x27,\r
351 0x3f, 0xc1, 0x4d }</Guid>\r
352 <Entry Name="UsbHc">\r
353 <C_Name>gEfiUsbHcProtocolGuid</C_Name>\r
354 <Guid>{ 0xf5089266, 0x1aa0, 0x4953, 0x97, 0xd8, 0x56, 0x2f, 0x8a,\r
355 0x73, 0xb5, 0x19 }</Guid>\r
aa0bf4f4 356\r
3585) Declare a new PPI in a package:\r
359 - This release requires manual editing of the SPD file\r
360 - Add the PPI .h file to the Include\Ppi directory.\r
64fcaead 361 - Add an <Entry> to the package <PpiDeclarations> element in the \r
362 <PackageName>.spd file\r
aa0bf4f4 363 * Each line contains PPI base name then the global variable name and then\r
364 the hex value of the PPI GUID.\r
64fcaead 366Example Ppi Entries (NOTE: The Guid entry is a single line in the SPD file):\r
368 <Entry Name="NtPeiLoadFile">\r
369 <C_Name>gNtPeiLoadFilePpiGuid</C_Name>\r
370 <Guid>{ 0xfd0c65eb, 0x405, 0x4cd2, 0x8a, 0xee, 0xf4, 0x0, 0xef, 0x13,\r
371 0xba, 0xc2 }</Guid>\r
372 </Entry>\r
373 <Entry Name="NtThunk">\r
374 <C_Name>gPeiNtThunkPpiGuid</C_Name>\r
375 <Guid>{ 0x98c281e5, 0xf906, 0x43dd, 0xa9, 0x2b, 0xb0, 0x3, 0xbf,\r
376 0x27, 0x65, 0xda }</Guid>\r
377 </Entry>\r
aa0bf4f4 380\r
3826) Declare a new GUID in a package:\r
383 - This release requires manual editing of the SPD file to include the new\r
64fcaead 384 Guid. This is identical to adding a ProtocolDeclaration or PpiDeclaration\r
385 element as described above.\r
aa0bf4f4 386\r
387--------------------------------------- \r
64fcaead 3887) Define a new PCD entry in a package:\r
aa0bf4f4 389 - This release requires manual editing of the SPD file to include the new\r
64fcaead 390 PCD. New Pcd entries are added to the PcdDefinitions section of the\r
391 <PackageName>.spd file using the following example for the format:\r
392 NOTE: The hex <Token> value must be unique.\r
395 <PcdEntry ItemType="FIXED_AT_BUILD">\r
396 <C_Name>PcdMaximumUnicodeStringLength</C_Name>\r
397 <Token>0x00000001</Token>\r
398 <DatumType>UINT32</DatumType>\r
399 <DefaultValue>1000000</DefaultValue>\r
400 </PcdEntry>\r
aa0bf4f4 402 \r
4048) Declare a new Library Class:\r
405 - This release requires manual editing of the SPD file to include the new\r
64fcaead 406 Library Class. New Library Class entries are added to the \r
407 LibraryClassDeclarations seection of the <PackageName>.spd file using\r
408 the following example for the format:\r
411 <LibraryClassDeclaration>\r
412 <LibraryClass>BaseLib</LibraryClass>\r
413 <IncludeHeader>Include/Library/BaseLib.h</IncludeHeader>\r
414 </LibraryClassDeclaration>\r
aa0bf4f4 416\r
4189) Add a library instance to a package:\r
419 - This requires manual MSA and MBD file.\r
42210) Add a module to a package:\r
423 - This requires manual MSA and MBD editing\r
429The EDK 2.0 represents significant changes in the structure of the EDK.\r
430Therefore it is very difficult to isolate all of the changes of this version of\r
431the EDK with the previous (EDK 1.0) version.\r
433Of particular note:\r
4351) EDK 2.0 contains new hardware feature support for the ICH SMBUS Libraries.\r
436 These libraries are provided to make Memory Reference Code (MRC) development\r
437 easier.\r
1465cc8b 4382) The MDE Libraries - The MDE libraries represent significant changes in source\r
aa0bf4f4 439 (with only limited changes in functionality.) These new libraries conform\r
440 to the "MDE Library Specification". \r
4413) The Fat Binary and the EDK Shell Binary Packages are functionally identical\r
442 to the EDK 1.0 version.\r
4434) The EDK tools directory has been expanded to include more tools and more\r
444 tool functionality.\r
4455) The EDK NT32 section has been ported to the new build process, but\r
446 functionally remains the same as the EDK 1.0 version.\r
4476) The Application "HelloWorld" has been ported to EDK 2.0 as well.\r
450Virus scanned by McAfee VirusScan Enterprise 8.0.0, Virus Definitions 4718, no\r
451virus detected.\r