Point to the correct _tools_def.txt file.
[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* (http://www.microsoft.com)\r
50 or\r
51 GCC version 4.x or later (http://gcc.gnu.org)\r
53Assembler Tool Chain\r
54 Microsoft Macro Assembler, version 6.15 or later\r
55 or\r
56 GCC version 4.x or later\r
58Java Development Kit ( Java 5.0 or later)\r
59 Sun* jdk-1.5.0_04 or later (http://java.sun.com)\r
60 or\r
61 Bea Systems* jrockit-25.2.0-jdk1.5.0_03 or later (http://www.bea.com)\r
63Java Tools\r
64 Apache-ANT, version 1.6.5 or later (http://ant.apache.org)\r
65 Ant-contrib, version 1.0b2 or later (http://antcontrib.sourceforge.net)\r
66 Saxon8, version 8.1.1\r
67 (http://prdownloads.sourceforge.net/saxon/saxonb8-1-1.zip?download)\r
68 XMLBeans, version 2.1.0 or later (http://xmlbeans.apache.org) \r
70Other Tools\r
71 TortoiseSVN version 1.3.3. (http://tortoisesvn.tigris.org/)\r
73Optional Tools\r
75Compiler Tool Chains:\r
76 Intel C++ Compiler for Windows, ver. 9.0 or later (http://www.intel,com)\r
77 Intel C Compiler for EFI Byte Code, ver. 1.2 or later\r
78 Microsoft Driver Development Kit, version 3790.1830 or later\r
79 Microsoft ACPI Source Language Assembler, Version 1.0.13NT or later\r
80 Intel ACPI Component Architecture, version 20060113\r
83Notes On Required Tools (Source Control System)\r
85The EDK 2.0 is being managed by the Subversion Source Control on Tianocore.org.\r
86This software package provides speed, security, and additional features. The\r
87recommended client is TortoiseSVN version 1.3.3. \r
88 (Available at http://tortoisesvn.tigris.org/)\r
90There are instructions for the use of Subversion Source Control on the\r
91Tianocore.org website, as part of the checkout procedures.\r
93The URL of the EDK 2.0 repository is:\r
94 https://edk2.tianocore.org/svn/edk2/trunk/edk2\r
97Notes On Documentation\r
99The documents are being managed by the Subversion Source Control on\r
100Tianocore.org. The document repository is "docs" and must be checked out\r
101separately from the EDK 2.0 source tree. Refer to the checkout procedures on\r
102the Tianocore.org website for EDK 2.0.\r
104The URL of the document repository is:\r
105 https://edk2.tianocore.org/svn/edk2/trunk/docs\r
109Notes On Required Tools (MS Windows environment example)\r
111Software Installation Order:\r
112 After installing the compiler tools and your Subversion client, the following\r
113 required tools should be installed in order: \r
114 Java JDK, Apache-Ant, ant-contrib, xmlbeans, saxon8\r
116Java Development Kit:\r
117 \r
118 The Java Environment Variable must be set before attempting to build.\r
119 i.e. For Sun JDK (see note below*):\r
120 set JAVA_HOME=c:\ Java\jdk1.5.0_06 \r
121 i.e. For Bea Systems:\r
122 set JAVA_HOME=c:\Program Files\Java\jrockit-R26.0.0-jdk1.5.0_04\r
123 \r
124 *When using the Sun JDK5.0\r
125 During installation, you should specify the install directory as C:\Java\r
126 instead of C:\Program Files\(or some other drive letter.) While installing\r
127 to this non-standard location is not required. In use, it seems to work \r
128 more reliably. \r
129 For the JDK, the install path would be C:\Java\jdk1.5.0_06\r
130 For the JRE, the install path would be C:\Java\jre1.5.0_06\r
131 Alternatively, you can specify C:\sunjavajdk and C:\sunjavajre.\r
01d2ed5e 132\r
aa0bf4f4 133 NOTE: You cannot combine the location for the JDK and the JRE, as the JRE\r
134 install removes most of the binaries and libraries installed by the JDK\r
135 install.\r
137Java Tools:\r
138 The Apache-ANT requires the ANT_HOME environment variable to be set before\r
139 attempting to build:\r
01d2ed5e 140 i.e. set ANT_HOME=c:\<full path to where ant was installed>\r
aa0bf4f4 141\r
142 The ant-contrib.jar file should be installed in the %ANT_HOME%\lib \r
143 directory.\r
145 The XMLBeans, requires the XMLBEANS_HOME environment variable to be set\r
146 before attempting to build:\r
01d2ed5e 147 i.e. set XMLBEANS_HOME=C:\<full path to where xmlbeans was installed>\r
aa0bf4f4 148\r
149 The saxon8.jar file should be copied to the %XMLBEANS_HOME%\lib directory.\r
151 The Ant and XMLBean tools are required to be in the path.\r
152 MS system example:\r
153 set PATH=%PATH%;%ANT_HOME%\bin;%XMLBEANS_HOME%\bin\r
154 Linux/OS X bash shell example:\r
155 export PATH=$PATH:${ANT_HOME}/bin:${XMLBEANS_HOME}/bin\r
156 \r
158Quick Start\r
54a1ec66 160Edit the text file, msft_tools_def.txt, located in the Tools/Conf directory.\r
161This file contains the names of the compiler tool chains and the location of\r
162the compiler binaries. It has been pre-populated with the standard location\r
163for the Microsoft tool chains and includes the standard location of the Intel C\r
aa0bf4f4 164Compiler for EFI Byte Code (EBC)\r
165 \r
166Follow the instructions at https://edk2.tianocore.org/servlets/ProjectSource to\r
167checkout the entire EDK 2.0 source tree.\r
169In a command window, change to the top level directory of the Edk 2.0 sources.\r
170 Set the WORKSPACE environment variable, e.g.:\r
172 c:\> set WORKSPACE=C:\MyWork\Edk2.0\r
174To test your tool chain setup and to build the Supplied Tools, execute:\r
175 c:\MyWork\Edk2.0\> edksetup\r
177(This command will be referred to as the setup command throughout the rest of\r
178this document.)\r
179 NOTE: You should run the setup command at the start of every session.\r
180 This configures the environment to include the TianoTools and the\r
181 Java applications and libraries.\r
183Once this is completed, you are ready to test the Build, by executing:\r
184 c:\MyWork\Edk2.0\> ant\r
186This command builds all of the packages, including the NT32 reference platform.\r
189Individual Package Builds\r
191After running the setup command, you can build individual packages.\r
192 In the command window, cd to the package that you want to build, and just\r
193 type:\r
194 c:\MyWork\Edk2.0\EdkNt32Pkg\> ant\r
196The EdkNt32Pkg has a special target; "run" that will execute the Nt32 emulation\r
197platform under Microsoft Windows.\r
200Individual Module Builds\r
202After running the setup command, you can build individual modules.\r
203 In the command window, cd to the module that you want to build, and just\r
204 type:\r
205 c:\MyWork\Edk2.0\MdePkg\Library\BaseLib\> ant\r
208A Word on Apache-ANT\r
210The Apache-ANT program is a build tool that uses XML-based project files.\r
211Similar to Makefiles, these project files may contain multiple targets. Most\r
212build.xml files in Edk2.0 are auto-generated; any edits performed on the\r
213build.xml files will be overwritten the next time ant is executed.\r
215Pre-defined targets in the build.xml files include:\r
216 all - This target builds binaries for defined architectures\r
217 clean - This target removes object files generated by commands\r
218 cleanall - This target removes all generated files and directories.\r
220A Word on GCC tool chain\r
222You will find a script in the tree that will download, configure, compile, and\r
223install a gcc 4.0.2 tool chain for development. It has support for the ia32\r
224architecture. It can be built and run on Cygwin, Linux, and many other POSIX\r
225compliant host environments. There are a few tools that you will need on your\r
226host computer in order to compile the tool chain. Among them are bash, gcc,\r
227gmake, curl (or wget).\r
231General Information:\r
232=============================================================== \r
235A quick understanding:\r
237A) Surface Area Package Description (SPD) file contains information about the\r
238modules that the package contains, including the location of all MSA files, and\r
239public library names and headers that might be provided by a module in the\r
240package. Packages are defined by SPD files. (Found in the root of the Package\r
241subdirectory (i.e. EdkNt32Pkg)) The SPD is further explained in the "Build \r
242Packaging Specification" document.\r
243 \r
244B) Module Surface Area Definition (MSA) files. A description of a module's \r
245surface area, with all module specific default flags and features specified.\r
246Refer to the "Module Surface Area Architecture Specification" for additional\r
247details. The MSA is further explained in the "Build Packaging Specification"\r
249 \r
250C) Module Build Description (MDB). The "as-built" definition file that contains\r
251only the changes to the default flags defined in the MSA. The MSA and MDB are\r
252further explained in the "Build Packaging Specification" document.\r
254D) Platform Configuration Database (PCD). A platform database which contains a\r
255variety of current platform settings or directives by which a driver or\r
256application can interact with. The PCD is defined by the PCD_Protocol (This is\r
257further explained in the "Platform Configuration Database Infrastructure \r
258Description" document.\r
260E) Library Class. A library class is a logical grouping of similar functions.\r
261When developing components, the module surface area declares the class of\r
262libraries that can be used by the component. The MBD file specifies the\r
263instance(s) of the library that will be used during compilation/linking. All\r
264library type modules must include header files in their distribution package,\r
265as well as their surface area and module build description files. Components,\r
266on the other hand, need only provide the binary and build description files\r
267when distributing BINARY packages. The Library Classes are further explained\r
268in the "Build Packaging Specification" document.\r
271The common operations by developers of new modules are:\r
2741) How to manually create a new module in a package:\r
275 - The module source code must first be created in an appropriate directory\r
276 (under the package the module is to be a part of.) \r
277 - An MSA file must be created, spelling out all aspects of the module.\r
278 - The MSA must be added to the SPD for the package to include the module.\r
2812) Add/Remove module(s) to/from a package:\r
283 - Setup environment as Build\r
284 - Add a module to a package\r
285 * Generate the module SurfaceArea description file and build description\r
286 file\r
287 * Run GenBuildFile.bat under <PackageDir> to generate an entrance\r
288 build.xml for the module\r
289 * Add a new <MsaFile> element under <MsaFiles> into\r
290 <PackageDir>\<PackageName>.spd, using relative path to package\r
291 * Add a new <ModuleSA> entry under each <TianoImage> into\r
292 <PackageDir>\<PackageName>.fpd file\r
294 - Remove a module from a package\r
295 * Comment out or remove corresponding <MsaFile> element under <MsaFiles>\r
296 from <PackageDir>\<PackageName>.spd\r
297 * Comment out or remove corresponding <ModuleSA> entry under each\r
298 <TianoImage> from <PackageDir>\<PackageName>.fpd\r
3013) How to manually create a package:\r
302 - Identify the modules that are to be members of the project.\r
303 - Identify the Variables and Guids required in and of the Package (including\r
304 consumption/production information).\r
305 - Create an SPD file defining these modules and calling out their MSA files.\r
3084) Declare a new Protocol in a package: \r
309 - This release requires manual editing of the SPD file, adding the protocol\r
310 to the ProtocolDeclarations section of the file. \r
311 - Add the Protocol .h file to the Include\Protocol directory.\r
64fcaead 312 - Add an <Entry> to the <ProtocolDeclarations> element in the \r
313 <PackageName>.spd file\r
aa0bf4f4 314 * Each line contains Protocol base name then the global variable name and\r
315 then the hex value of the Protocol GUID.\r
64fcaead 317Example Protocol Entries (NOTE: The Guid entry is a single line in the SPD file):\r
319 <Entry Name="UnicodeCollation">\r
320 <C_Name>gEfiUnicodeCollationProtocolGuid</C_Name>\r
321 <Guid>{ 0x1d85cd7f, 0xf43d, 0x11d2, 0x9a, 0xc, 0x0, 0x90, 0x27,\r
322 0x3f, 0xc1, 0x4d }</Guid>\r
323 <Entry Name="UsbHc">\r
324 <C_Name>gEfiUsbHcProtocolGuid</C_Name>\r
325 <Guid>{ 0xf5089266, 0x1aa0, 0x4953, 0x97, 0xd8, 0x56, 0x2f, 0x8a,\r
326 0x73, 0xb5, 0x19 }</Guid>\r
aa0bf4f4 327\r
3295) Declare a new PPI in a package:\r
330 - This release requires manual editing of the SPD file\r
331 - Add the PPI .h file to the Include\Ppi directory.\r
64fcaead 332 - Add an <Entry> to the package <PpiDeclarations> element in the \r
333 <PackageName>.spd file\r
aa0bf4f4 334 * Each line contains PPI base name then the global variable name and then\r
335 the hex value of the PPI GUID.\r
64fcaead 337Example Ppi Entries (NOTE: The Guid entry is a single line in the SPD file):\r
339 <Entry Name="NtPeiLoadFile">\r
340 <C_Name>gNtPeiLoadFilePpiGuid</C_Name>\r
341 <Guid>{ 0xfd0c65eb, 0x405, 0x4cd2, 0x8a, 0xee, 0xf4, 0x0, 0xef, 0x13,\r
342 0xba, 0xc2 }</Guid>\r
343 </Entry>\r
344 <Entry Name="NtThunk">\r
345 <C_Name>gPeiNtThunkPpiGuid</C_Name>\r
346 <Guid>{ 0x98c281e5, 0xf906, 0x43dd, 0xa9, 0x2b, 0xb0, 0x3, 0xbf,\r
347 0x27, 0x65, 0xda }</Guid>\r
348 </Entry>\r
aa0bf4f4 351\r
3536) Declare a new GUID in a package:\r
354 - This release requires manual editing of the SPD file to include the new\r
64fcaead 355 Guid. This is identical to adding a ProtocolDeclaration or PpiDeclaration\r
356 element as described above.\r
aa0bf4f4 357\r
358--------------------------------------- \r
64fcaead 3597) Define a new PCD entry in a package:\r
aa0bf4f4 360 - This release requires manual editing of the SPD file to include the new\r
64fcaead 361 PCD. New Pcd entries are added to the PcdDefinitions section of the\r
362 <PackageName>.spd file using the following example for the format:\r
363 NOTE: The hex <Token> value must be unique.\r
366 <PcdEntry ItemType="FIXED_AT_BUILD">\r
367 <C_Name>PcdMaximumUnicodeStringLength</C_Name>\r
368 <Token>0x00000001</Token>\r
369 <DatumType>UINT32</DatumType>\r
370 <DefaultValue>1000000</DefaultValue>\r
371 </PcdEntry>\r
aa0bf4f4 373 \r
3758) Declare a new Library Class:\r
376 - This release requires manual editing of the SPD file to include the new\r
64fcaead 377 Library Class. New Library Class entries are added to the \r
378 LibraryClassDeclarations seection of the <PackageName>.spd file using\r
379 the following example for the format:\r
382 <LibraryClassDeclaration>\r
383 <LibraryClass>BaseLib</LibraryClass>\r
384 <IncludeHeader>Include/Library/BaseLib.h</IncludeHeader>\r
385 </LibraryClassDeclaration>\r
aa0bf4f4 387\r
3899) Add a library instance to a package:\r
390 - This requires manual MSA and MBD file.\r
39310) Add a module to a package:\r
394 - This requires manual MSA and MBD editing\r
400The EDK 2.0 represents significant changes in the structure of the EDK.\r
401Therefore it is very difficult to isolate all of the changes of this version of\r
402the EDK with the previous (EDK 1.0) version.\r
404Of particular note:\r
4061) EDK 2.0 contains new hardware feature support for the ICH SMBUS Libraries.\r
407 These libraries are provided to make Memory Reference Code (MRC) development\r
408 easier.\r
1465cc8b 4092) The MDE Libraries - The MDE libraries represent significant changes in source\r
aa0bf4f4 410 (with only limited changes in functionality.) These new libraries conform\r
411 to the "MDE Library Specification". \r
4123) The Fat Binary and the EDK Shell Binary Packages are functionally identical\r
413 to the EDK 1.0 version.\r
4144) The EDK tools directory has been expanded to include more tools and more\r
415 tool functionality.\r
4165) The EDK NT32 section has been ported to the new build process, but\r
417 functionally remains the same as the EDK 1.0 version.\r
4186) The Application "HelloWorld" has been ported to EDK 2.0 as well.\r
421Virus scanned by McAfee VirusScan Enterprise 8.0.0, Virus Definitions 4718, no\r
422virus detected.\r