]>
Commit | Line | Data |
---|---|---|
aa0bf4f4 | 1 | Intel(R) Platform Innovation Framework for EFI\r |
e3f236c8 | 2 | EFI Development Kit 2.0 (EDK II) \r |
aa0bf4f4 | 3 | Alpha Release\r |
e3f236c8 | 4 | 2006-04-26\r |
aa0bf4f4 | 5 | \r |
6 | Copyright (c) 2006, Intel Corporation\r | |
7 | \r | |
8 | This document provides updates to documentation, along with a description on \r | |
e3f236c8 | 9 | how to install and build the Edk II.\r |
aa0bf4f4 | 10 | \r |
11 | Package Contents\r | |
12 | ----------------\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 | |
23 | \r | |
24 | Note: MDE and MDK that appear in other documentation refer to the MdePkg and\r | |
25 | Tools packages. These two packages are the minimum requirement for developing\r | |
13421853 | 26 | EDK II Packages. It is also recommended that the top level files included\r |
aa0bf4f4 | 27 | with the EDK be downloaded in conjunction with these two packages.\r |
28 | \r | |
29 | Note: Documents have the following filenames:\r | |
13421853 | 30 | EDK II Module Development Environment Library Specification v0.50 \r |
aa0bf4f4 | 31 | (MDE_Library_Spec_0_50.rtf)\r |
13421853 | 32 | EDK II Build and Packaging Architecture Specification v0.50\r |
aa0bf4f4 | 33 | (Build_Packaging_Spec_0_50.rtf)\r |
13421853 | 34 | EDK II Platform Configuration Database Infrastructure Description v0.51\r |
aa0bf4f4 | 35 | (PCD_Infrastructure_0_51.rtf)\r |
13421853 | 36 | EDK II Module Surface Area v0.50\r |
aa0bf4f4 | 37 | (Module_Surface_Area_0_50.rtf)\r |
13421853 | 38 | EDK II Module Development Environment (MDE) Package Specification v0.50\r |
aa0bf4f4 | 39 | (MDE_Package_Spec_0_50.rtf)\r |
13421853 | 40 | EDK II C Coding Standards Specification v0.50\r |
aa0bf4f4 | 41 | (C_Coding_Standards_Specification_ 0_50.rtf)\r |
42 | \r | |
43 | Pre-Requisites\r | |
44 | --------------\r | |
45 | The following list of tools must be installed on the development workstation\r | |
e3f236c8 | 46 | prior to using the Edk II.\r |
aa0bf4f4 | 47 | \r |
48 | Compiler Tool Chain\r | |
49 | Microsoft* Visual Studio .NET 2003* (http://www.microsoft.com)\r | |
50 | or\r | |
43475442 | 51 | A special GCC version 4.x or later (http://gcc.gnu.org). See below.\r |
aa0bf4f4 | 52 | \r |
53 | Assembler 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 |
58 | Java 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 | |
62 | \r | |
63 | Java Tools\r | |
64 | Apache-ANT, version 1.6.5 or later (http://ant.apache.org)\r | |
50518883 | 65 | Ant-contrib, version 1.0b2 or later\r |
66 | (http://sourceforge.net/project/showfiles.php?group_id=36177)\r | |
aa0bf4f4 | 67 | Saxon8, version 8.1.1\r |
68 | (http://prdownloads.sourceforge.net/saxon/saxonb8-1-1.zip?download)\r | |
69 | XMLBeans, version 2.1.0 or later (http://xmlbeans.apache.org) \r | |
70 | \r | |
71 | Other Tools\r | |
72 | TortoiseSVN version 1.3.3. (http://tortoisesvn.tigris.org/)\r | |
73 | \r | |
74 | Optional Tools\r | |
75 | --------------\r | |
76 | Compiler Tool Chains:\r | |
50518883 | 77 | Intel C++ Compiler for Windows, ver. 9.0 or later (http://www.intel.com)\r |
8fb9e6b8 | 78 | Intel C Compiler for EFI Byte Code, ver. 1.2 or later \r |
79 | (http://www.intel.com/cd/software/products/asmo-na/eng/compilers/efibc/index.htm)\r | |
aa0bf4f4 | 80 | Microsoft Driver Development Kit, version 3790.1830 or later\r |
8fb9e6b8 | 81 | (http://www.microsoft.com/whdc/devtools/ddk/orderddkcd.mspx)\r |
aa0bf4f4 | 82 | Microsoft ACPI Source Language Assembler, Version 1.0.13NT or later\r |
83 | Intel ACPI Component Architecture, version 20060113\r | |
84 | \r | |
85 | -----------------------\r | |
86 | Notes On Required Tools (Source Control System)\r | |
87 | -----------------------\r | |
13421853 | 88 | The EDK II is being managed by the Subversion Source Control on Tianocore.org.\r |
aa0bf4f4 | 89 | This software package provides speed, security, and additional features. The\r |
90 | recommended client is TortoiseSVN version 1.3.3. \r | |
91 | (Available at http://tortoisesvn.tigris.org/)\r | |
92 | \r | |
93 | There are instructions for the use of Subversion Source Control on the\r | |
94 | Tianocore.org website, as part of the checkout procedures.\r | |
95 | \r | |
13421853 | 96 | The URL of the EDK II repository is:\r |
aa0bf4f4 | 97 | https://edk2.tianocore.org/svn/edk2/trunk/edk2\r |
98 | \r | |
99 | -----------------------\r | |
100 | Notes On Documentation\r | |
101 | -----------------------\r | |
102 | The documents are being managed by the Subversion Source Control on\r | |
103 | Tianocore.org. The document repository is "docs" and must be checked out\r | |
13421853 | 104 | separately from the EDK II source tree. Refer to the checkout procedures on\r |
105 | the Tianocore.org website for EDK II.\r | |
aa0bf4f4 | 106 | \r |
107 | The URL of the document repository is:\r | |
108 | https://edk2.tianocore.org/svn/edk2/trunk/docs\r | |
109 | \r | |
110 | \r | |
111 | -----------------------\r | |
112 | Notes On Required Tools (MS Windows environment example)\r | |
113 | -----------------------\r | |
114 | Software 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 | |
118 | \r | |
119 | Java 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 | |
139 | \r | |
140 | Java 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 | |
147 | \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 | |
153 | \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 | |
160 | -------------------------------------------------------------------------------\r | |
161 | Quick Start\r | |
162 | -----------\r | |
e3f236c8 | 163 | Edit the text file, target.txt, located in the Tools/Conf directory. This \r |
164 | file contains the tools defintion file and ative platform. It can also restrict\r | |
165 | current build target(s), tagname(s) and arch(s). Uncomment the line ACTIVE_PLATFORM\r | |
166 | which is commented out by default. \r | |
167 | \r | |
168 | Edit the tools definition file, tools_def.txt, also located in the Tools/Conf \r | |
169 | directory. This file contains the names of the compiler tool chains and the \r | |
170 | location of the compiler binaries. It has been pre-populated with the standard \r | |
171 | location for the Microsoft tool chains and includes the standard location of \r | |
172 | the Intel C Compiler for EFI Byte Code (EBC)\r | |
aa0bf4f4 | 173 | \r |
174 | Follow the instructions at https://edk2.tianocore.org/servlets/ProjectSource to\r | |
13421853 | 175 | checkout the entire EDK II source tree.\r |
aa0bf4f4 | 176 | \r |
e3f236c8 | 177 | In a command window, change to the top level directory of the Edk II sources.\r |
aa0bf4f4 | 178 | Set the WORKSPACE environment variable, e.g.:\r |
179 | \r | |
180 | c:\> set WORKSPACE=C:\MyWork\Edk2.0\r | |
181 | \r | |
182 | To test your tool chain setup and to build the Supplied Tools, execute:\r | |
183 | c:\MyWork\Edk2.0\> edksetup\r | |
184 | \r | |
185 | (This command will be referred to as the setup command throughout the rest of\r | |
186 | this document.)\r | |
187 | NOTE: You should run the setup command at the start of every session.\r | |
188 | This configures the environment to include the TianoTools and the\r | |
189 | Java applications and libraries.\r | |
190 | \r | |
191 | Once this is completed, you are ready to test the Build, by executing:\r | |
e3f236c8 | 192 | c:\MyWork\Edk2.0\> build\r |
aa0bf4f4 | 193 | \r |
e3f236c8 | 194 | This command builds active platform specified in text file target.txt. If \r |
195 | active platform is not specified, go to sub-directory which contains FPD files and\r | |
196 | type build. More information about active platform policy reference to specification\r | |
197 | <<EDK II Build and Packaging Architecture Specification>>.\r | |
90f7b6a8 | 198 | \r |
aa0bf4f4 | 199 | -------------------------\r |
e3f236c8 | 200 | Individual Platform Builds\r |
aa0bf4f4 | 201 | -------------------------\r |
e3f236c8 | 202 | After running the setup command, you can build individual platforms.\r |
203 | In the command window, \r | |
204 | 1. Set active platform in target.txt, and type "build" in whatever directory;\r | |
205 | 2. or cd to the platform (FPD file) that you want to build, and just type:\r | |
206 | c:\MyWork\Edk2.0\EdkNt32Pkg\> build\r | |
207 | \r | |
208 | Note that active platform with the high priority to build, that means active \r | |
209 | platform will be built even if exists FPD file under current directory. More \r | |
210 | information about active platform policy reference to specification\r | |
211 | <<EDK II Build and Packaging Architecture Specification>>. \r | |
aa0bf4f4 | 212 | \r |
e3f236c8 | 213 | Go to <full build path>\Debug\MSFT\IA32 and execute SecMain.exe\r |
214 | to run the Nt32 emulation platform under Microsoft Windows.\r | |
aa0bf4f4 | 215 | \r |
03fed93e | 216 | To exit the Nt32 emulation platform, you may type reset at the EFI Shell>\r |
217 | command prompt. Alternately, you may use the Graphical interface, Boot\r | |
218 | Maintenance Manager screen's Reset System command.\r | |
219 | \r | |
aa0bf4f4 | 220 | ------------------------\r |
221 | Individual Module Builds\r | |
222 | ------------------------\r | |
223 | After running the setup command, you can build individual modules.\r | |
224 | In the command window, cd to the module that you want to build, and just\r | |
225 | type:\r | |
e3f236c8 | 226 | c:\MyWork\Edk2.0\MdePkg\Library\BaseLib\> build\r |
227 | \r | |
228 | Note active platform must be set for individual module build. \r | |
aa0bf4f4 | 229 | \r |
230 | -------------------------------------------------------------------------------\r | |
231 | A Word on Apache-ANT\r | |
232 | --------------------\r | |
233 | The Apache-ANT program is a build tool that uses XML-based project files.\r | |
234 | Similar to Makefiles, these project files may contain multiple targets. Most\r | |
e3f236c8 | 235 | build.xml files in Edk2.0 are auto-generated; any edits performed on the\r |
aa0bf4f4 | 236 | build.xml files will be overwritten the next time ant is executed.\r |
237 | \r | |
238 | Pre-defined targets in the build.xml files include:\r | |
239 | all - This target builds binaries for defined architectures\r | |
240 | clean - This target removes object files generated by commands\r | |
241 | cleanall - This target removes all generated files and directories.\r | |
242 | \r | |
243 | A Word on GCC tool chain\r | |
244 | ------------------------\r | |
e3f236c8 | 245 | EDK2 will not compile with a standard Linux gcc tool chain. While Linux\r |
246 | distributions are usually based on ELF, EDK2 requires a version of gcc that is\r | |
43475442 | 247 | configured to produce PE-COFF images. You will find a script in edk2/Tools/gcc\r |
248 | that will download, configure, compile, and install a gcc 4.X cross-compile\r | |
e3f236c8 | 249 | tool chain for EDK2 development. It has support for the ia32 architecture. It\r |
43475442 | 250 | can be built and run on Cygwin, Linux, and many other POSIX compliant host\r |
251 | operating environments. There are a few tools that you will need on your host\r | |
252 | computer in order to compile the tool chain. Among them are bash, gcc, gmake,\r | |
253 | curl (or wget).\r | |
aa0bf4f4 | 254 | \r |
255 | -------------------------------------------------------------------------------\r | |
256 | \r | |
257 | General Information:\r | |
258 | =============================================================== \r | |
259 | Mechanisms:\r | |
260 | ----------\r | |
8fb9e6b8 | 261 | A brief overview:\r |
aa0bf4f4 | 262 | \r |
263 | A) Surface Area Package Description (SPD) file contains information about the\r | |
264 | modules that the package contains, including the location of all MSA files, and\r | |
265 | public library names and headers that might be provided by a module in the\r | |
266 | package. Packages are defined by SPD files. (Found in the root of the Package\r | |
267 | subdirectory (i.e. EdkNt32Pkg)) The SPD is further explained in the "Build \r | |
268 | Packaging Specification" document.\r | |
269 | \r | |
270 | B) Module Surface Area Definition (MSA) files. A description of a module's \r | |
271 | surface area, with all module specific default flags and features specified.\r | |
272 | Refer to the "Module Surface Area Architecture Specification" for additional\r | |
273 | details. The MSA is further explained in the "Build Packaging Specification"\r | |
274 | document.\r | |
275 | \r | |
276 | C) Module Build Description (MDB). The "as-built" definition file that contains\r | |
277 | only the changes to the default flags defined in the MSA. The MSA and MDB are\r | |
278 | further explained in the "Build Packaging Specification" document.\r | |
279 | \r | |
280 | D) Platform Configuration Database (PCD). A platform database which contains a\r | |
281 | variety of current platform settings or directives by which a driver or\r | |
282 | application can interact with. The PCD is defined by the PCD_Protocol (This is\r | |
283 | further explained in the "Platform Configuration Database Infrastructure \r | |
284 | Description" document.\r | |
285 | \r | |
286 | E) Library Class. A library class is a logical grouping of similar functions.\r | |
287 | When developing components, the module surface area declares the class of\r | |
288 | libraries that can be used by the component. The MBD file specifies the\r | |
289 | instance(s) of the library that will be used during compilation/linking. All\r | |
290 | library type modules must include header files in their distribution package,\r | |
291 | as well as their surface area and module build description files. Components,\r | |
292 | on the other hand, need only provide the binary and build description files\r | |
293 | when distributing BINARY packages. The Library Classes are further explained\r | |
294 | in the "Build Packaging Specification" document.\r | |
295 | \r | |
296 | =========================================================================\r | |
297 | The common operations by developers of new modules are:\r | |
298 | -------------------------------------------------------\r | |
299 | \r | |
300 | 1) How to manually create a new module in a package:\r | |
301 | - The module source code must first be created in an appropriate directory\r | |
302 | (under the package the module is to be a part of.) \r | |
303 | - An MSA file must be created, spelling out all aspects of the module.\r | |
304 | - The MSA must be added to the SPD for the package to include the module.\r | |
305 | \r | |
306 | -----------------------------------------\r | |
307 | 2) Add/Remove module(s) to/from a package:\r | |
308 | \r | |
309 | - Setup environment as Build\r | |
310 | - Add a module to a package\r | |
e3f236c8 | 311 | * Generate the module SurfaceArea description file\r |
312 | * Add a new <Filename> element under <MsaFiles> into\r | |
aa0bf4f4 | 313 | <PackageDir>\<PackageName>.spd, using relative path to package\r |
e3f236c8 | 314 | * Add a new <ModuleSA> entry under each <FrameworkModules> into\r |
315 | <PackageDir>\<PackageName>.fpd file if necessary. \r | |
aa0bf4f4 | 316 | \r |
317 | - Remove a module from a package\r | |
e3f236c8 | 318 | * Comment out or remove corresponding <Filename> element under <MsaFiles>\r |
aa0bf4f4 | 319 | from <PackageDir>\<PackageName>.spd\r |
320 | * Comment out or remove corresponding <ModuleSA> entry under each\r | |
e3f236c8 | 321 | <FrameworkModules> from <PackageDir>\<PackageName>.fpd if necessary. \r |
aa0bf4f4 | 322 | \r |
323 | -----------------------------------\r | |
324 | 3) How to manually create a package:\r | |
325 | - Identify the modules that are to be members of the project.\r | |
326 | - Identify the Variables and Guids required in and of the Package (including\r | |
327 | consumption/production information).\r | |
328 | - Create an SPD file defining these modules and calling out their MSA files.\r | |
e3f236c8 | 329 | - add a new <Filename> element under <PackageList> into \r |
330 | Tools\Conf\FrameworkDatabase.db, using the relative path to workspace. \r | |
aa0bf4f4 | 331 | \r |
332 | --------------------------------------\r | |
333 | 4) Declare a new Protocol in a package: \r | |
334 | - This release requires manual editing of the SPD file, adding the protocol\r | |
335 | to the ProtocolDeclarations section of the file. \r | |
336 | - Add the Protocol .h file to the Include\Protocol directory.\r | |
64fcaead | 337 | - Add an <Entry> to the <ProtocolDeclarations> element in the \r |
338 | <PackageName>.spd file\r | |
aa0bf4f4 | 339 | * Each line contains Protocol base name then the global variable name and\r |
340 | then the hex value of the Protocol GUID.\r | |
341 | \r | |
64fcaead | 342 | Example Protocol Entries (NOTE: The Guid entry is a single line in the SPD file):\r |
343 | <ProtocolDeclarations>\r | |
e3f236c8 | 344 | <Entry Name="Bds">\r |
345 | <C_Name>gEfiBdsArchProtocolGuid</C_Name>\r | |
346 | <GuidValue>665E3FF6-46CC-11D4-9A38-0090273FC14D</GuidValue>\r | |
347 | <HelpText/>\r | |
348 | </Entry>\r | |
349 | <Entry Name="Cpu">\r | |
350 | <C_Name>gEfiCpuArchProtocolGuid</C_Name>\r | |
351 | <GuidValue>26BACCB1-6F42-11D4-BCE7-0080C73C8881</GuidValue>\r | |
352 | <HelpText/>\r | |
353 | </Entry>\r | |
354 | </ProtocolDeclarations>\r | |
aa0bf4f4 | 355 | \r |
356 | ---------------------------------\r | |
357 | 5) Declare a new PPI in a package:\r | |
358 | - This release requires manual editing of the SPD file\r | |
359 | - Add the PPI .h file to the Include\Ppi directory.\r | |
64fcaead | 360 | - Add an <Entry> to the package <PpiDeclarations> element in the \r |
361 | <PackageName>.spd file\r | |
aa0bf4f4 | 362 | * Each line contains PPI base name then the global variable name and then\r |
363 | the hex value of the PPI GUID.\r | |
364 | \r | |
64fcaead | 365 | Example Ppi Entries (NOTE: The Guid entry is a single line in the SPD file):\r |
366 | <PpiDeclarations>\r | |
e3f236c8 | 367 | <Entry Name="BootInRecoveryMode">\r |
368 | <C_Name>gEfiPeiBootInRecoveryModePpiGuid</C_Name>\r | |
369 | <GuidValue>17EE496A-D8E4-4B9A-94D1-CE8272300850</GuidValue>\r | |
370 | <HelpText/>\r | |
64fcaead | 371 | </Entry>\r |
e3f236c8 | 372 | <Entry Name="CpuIo">\r |
373 | <C_Name>gEfiPeiCpuIoPpiInServiceTableGuid</C_Name>\r | |
374 | <GuidValue>E6AF1F7B-FC3F-46DA-A828-A3B457A44282</GuidValue>\r | |
375 | <HelpText/>\r | |
64fcaead | 376 | </Entry>\r |
377 | </PpiDeclarations>\r | |
378 | \r | |
aa0bf4f4 | 379 | ----------------------------------\r |
380 | 6) Declare a new GUID in a package:\r | |
381 | - This release requires manual editing of the SPD file to include the new\r | |
64fcaead | 382 | Guid. This is identical to adding a ProtocolDeclaration or PpiDeclaration\r |
383 | element as described above.\r | |
aa0bf4f4 | 384 | \r |
385 | --------------------------------------- \r | |
64fcaead | 386 | 7) Define a new PCD entry in a package:\r |
aa0bf4f4 | 387 | - This release requires manual editing of the SPD file to include the new\r |
64fcaead | 388 | PCD. New Pcd entries are added to the PcdDefinitions section of the\r |
389 | <PackageName>.spd file using the following example for the format:\r | |
390 | NOTE: The hex <Token> value must be unique.\r | |
391 | \r | |
392 | <PcdDefinitions>\r | |
393 | <PcdEntry ItemType="FIXED_AT_BUILD">\r | |
394 | <C_Name>PcdMaximumUnicodeStringLength</C_Name>\r | |
395 | <Token>0x00000001</Token>\r | |
396 | <DatumType>UINT32</DatumType>\r | |
397 | <DefaultValue>1000000</DefaultValue>\r | |
398 | </PcdEntry>\r | |
399 | </PcdDefinition>\r | |
aa0bf4f4 | 400 | \r |
401 | ------------------------------\r | |
402 | 8) Declare a new Library Class:\r | |
403 | - This release requires manual editing of the SPD file to include the new\r | |
64fcaead | 404 | Library Class. New Library Class entries are added to the \r |
405 | LibraryClassDeclarations seection of the <PackageName>.spd file using\r | |
406 | the following example for the format:\r | |
407 | \r | |
408 | <LibraryClassDeclarations>\r | |
e3f236c8 | 409 | <LibraryClass Name="BaseLib">\r |
64fcaead | 410 | <IncludeHeader>Include/Library/BaseLib.h</IncludeHeader>\r |
e3f236c8 | 411 | <HelpText/>\r |
412 | </LibraryClass>\r | |
413 | <LibraryClass Name="BaseMemoryLib">\r | |
414 | <IncludeHeader>Include/Library/BaseMemoryLib.h</IncludeHeader>\r | |
415 | <HelpText/>\r | |
416 | </LibraryClass>\r | |
64fcaead | 417 | </LibraryClassDeclarations>\r |
aa0bf4f4 | 418 | \r |
aa0bf4f4 | 419 | =======================================================\r |
420 | Notes:\r | |
421 | ------\r | |
13421853 | 422 | The EDK II represents significant changes in the structure of the EDK.\r |
aa0bf4f4 | 423 | Therefore it is very difficult to isolate all of the changes of this version of\r |
424 | the EDK with the previous (EDK 1.0) version.\r | |
425 | \r | |
426 | Of particular note:\r | |
427 | \r | |
13421853 | 428 | 1) EDK II contains new hardware feature support for the ICH SMBUS Libraries.\r |
aa0bf4f4 | 429 | These libraries are provided to make Memory Reference Code (MRC) development\r |
430 | easier.\r | |
1465cc8b | 431 | 2) The MDE Libraries - The MDE libraries represent significant changes in source\r |
aa0bf4f4 | 432 | (with only limited changes in functionality.) These new libraries conform\r |
433 | to the "MDE Library Specification". \r | |
434 | 3) The Fat Binary and the EDK Shell Binary Packages are functionally identical\r | |
435 | to the EDK 1.0 version.\r | |
436 | 4) The EDK tools directory has been expanded to include more tools and more\r | |
437 | tool functionality.\r | |
438 | 5) The EDK NT32 section has been ported to the new build process, but\r | |
439 | functionally remains the same as the EDK 1.0 version.\r | |
13421853 | 440 | 6) The Application "HelloWorld" has been ported to EDK II as well.\r |
aa0bf4f4 | 441 | \r |
442 | =======================================================\r | |
443 | Virus scanned by McAfee VirusScan Enterprise 8.0.0, Virus Definitions 4718, no\r | |
444 | virus detected.\r | |
445 | \r |