]>
Commit | Line | Data |
---|---|---|
1 | Intel(R) Platform Innovation Framework for EFI\r | |
2 | EFI Development Kit II (EDK II)\r | |
3 | Root Package 1.00\r | |
4 | 2006-11-08\r | |
5 | \r | |
6 | Intel is a trademark or registered trademark of Intel Corporation or its\r | |
7 | subsidiaries in the United States and other countries.\r | |
8 | * Other names and brands may be claimed as the property of others.\r | |
9 | Copyright (c) 2006 - 2007, Intel Corporation\r | |
10 | \r | |
11 | This document provides updates to documentation, along with a description on\r | |
12 | how to install and build the EDK II.\r | |
13 | \r | |
14 | Package Contents\r | |
15 | ----------------\r | |
16 | BuildNotes.txt - The build notes for this package.\r | |
17 | OldMdePkg - Industry-standard headers and libraries\r | |
18 | Tools - Build -specific tools that are designed to help the\r | |
19 | developer create and modify drivers and libraries\r | |
20 | EdkModulePkg - Reference drivers\r | |
21 | EdkFatBinPkg - Binary DXE drivers for the Fat 32 file system\r | |
22 | EdkShellBinPkg - Binary Shell applications and commands\r | |
23 | EdkNt32Pkg - NT32 Emulation platform reference\r | |
24 | EdkUnixPkg - Posix/Unix Emulation platform reference (Currently this\r | |
25 | builds only on ia32 Linux, but is meant to be portable.)\r | |
26 | \r | |
27 | Note: MDE and MDK that appear in other documentation refer to the OldMdePkg and\r | |
28 | Tools packages, respectively. While, these two packages are the minimum\r | |
29 | requirement for developing EDK II Packages we recommend that you download all\r | |
30 | of the top-level files listed above.\r | |
31 | \r | |
32 | The following package is available as a separate project, under a separate\r | |
33 | license, on the TianoCore.org website: https://fat-driver2.tianocore.org\r | |
34 | \r | |
35 | EdkFatPkg - A package containing source DXE drivers for the Fat 32 file\r | |
36 | system\r | |
37 | \r | |
38 | Documents have the following filenames (to download these documents, see "Notes\r | |
39 | on Documentation" later in these Release Notes):\r | |
40 | EDK II Module Development Environment Library Specification, v0.58\r | |
41 | (MDE_Library_Spec_0_58.rtf)\r | |
42 | EDK II Build and Packaging Architecture Specification, v0.53\r | |
43 | (Build_Packaging_Spec_0_53.rtf)\r | |
44 | EDK II Platform Configuration Database Infrastructure Description, v0.54\r | |
45 | (PCD_Infrastructure_0_54.rtf)\r | |
46 | EDK II Module Surface Area Specification, v0.51\r | |
47 | (Module_Surface_Area_0_50.rtf)\r | |
48 | EDK II Module Development Environment Package Specification, v0.51\r | |
49 | (MDE_Package_Spec_0_51.rtf)\r | |
50 | EDK II C Coding Standards Specification v0.51\r | |
51 | (C_Coding_Standards_Specification_ 0_51.rtf)\r | |
52 | EDK II Subversion Setup Guide\r | |
53 | (edk2-subversion-setup.rtf)\r | |
54 | \r | |
55 | Pre-Requisites\r | |
56 | --------------\r | |
57 | The following list of tools must be installed on the development workstation\r | |
58 | prior to using the EDK II.\r | |
59 | \r | |
60 | Compiler Tool Chain\r | |
61 | Microsoft* Visual Studio .NET 2003* (http://www.microsoft.com)\r | |
62 | or\r | |
63 | A special GCC version 4.x or later (http://gcc.gnu.org). See below.\r | |
64 | \r | |
65 | Assembler Tool Chain\r | |
66 | Microsoft Macro Assembler, version 6.15 or later\r | |
67 | or\r | |
68 | GNU binutils 2.16.1 or later\r | |
69 | (Http://ftp.gnu.org/gnu/binutils)\r | |
70 | \r | |
71 | Java Development Kit ( Java 5.0 or later)\r | |
72 | Sun* jdk-1.5.0_06 or later (http://java.sun.com)\r | |
73 | or\r | |
74 | Bea Systems* jrockit-25.2.0-jdk1.5.0_03 or later (http://www.bea.com)\r | |
75 | \r | |
76 | Java Tools\r | |
77 | Apache-ANT, version 1.6.5 or later (http://ant.apache.org)\r | |
78 | Ant-contrib, version 1.0b2 or later\r | |
79 | (http://prdownloads.sourceforge.net/ant-contrib/ant-contrib-1.0b2-bin.zip?download)\r | |
80 | Saxon8, version 8.1.1\r | |
81 | (http://prdownloads.sourceforge.net/saxon/saxonb8-1-1.zip?download)\r | |
82 | XMLBeans, version 2.1.0 (http://xmlbeans.apache.org)\r | |
83 | DO NOT download the latest XMLBeans, version 2.2.0. It is not compatible\r | |
84 | with Saxon8, version 8.1.1.\r | |
85 | \r | |
86 | Other Tools\r | |
87 | TortoiseSVN version 1.3.3. (http://tortoisesvn.tigris.org/)\r | |
88 | \r | |
89 | Optional Tools\r | |
90 | --------------\r | |
91 | Compiler Tool Chains:\r | |
92 | Intel(R) C++ Compiler for Windows*, ver. 9.0 or later (http://www.intel.com)\r | |
93 | Intel(R) C Compiler for EFI Byte Code, ver. 1.2 or later\r | |
94 | (http://www.intel.com/cd/software/products/asmo-na/eng/compilers/efibc/index.htm)\r | |
95 | Microsoft Driver Development Kit, version 3790.1830 or later\r | |
96 | (http://www.microsoft.com/whdc/devtools/ddk/orderddkcd.mspx)\r | |
97 | Microsoft ACPI Source Language Assembler, Version 1.0.13NT or later\r | |
98 | Intel ACPI Component Architecture, version 20060113\r | |
99 | \r | |
100 | Python\r | |
101 | \r | |
102 | There are several tools implemented in Python and wxPython Widgets in the\r | |
103 | Tools/Python directory. These are optional tools, and are not necessary in\r | |
104 | order to use or build the edk2 code. In order to use them you must\r | |
105 | install Python 2.4.x and wxWidgets 2.8.x for your platform. The tools\r | |
106 | have been tested and work correctly on OS X, Linux and Windows.\r | |
107 | \r | |
108 | There is a script called Install_Python_OSX.sh that will download and\r | |
109 | install the correct versions for OS X. For other platforms, please find\r | |
110 | the installers for your platform at the following sites:\r | |
111 | \r | |
112 | - http://www.python.org/download/releases/2.4.4/ (Python interpreter)\r | |
113 | - http://www.wxpython.org/download.php#binaries (Python GUI extensions)\r | |
114 | \r | |
115 | Your linux distribution may contain packages of python and wxPython, which\r | |
116 | should work, provided they are are compatible with the above specified\r | |
117 | versions.\r | |
118 | \r | |
119 | -----------------------------------------------\r | |
120 | Notes on Required Tools (Source Control System)\r | |
121 | -----------------------------------------------\r | |
122 | The EDK II is being managed by the Subversion Source Control on Tianocore.org.\r | |
123 | Subversion provides speed, security, and additional features. The\r | |
124 | recommended client is TortoiseSVN version 1.3.3.\r | |
125 | (Available at http://tortoisesvn.tigris.org/)\r | |
126 | \r | |
127 | The checkout procedures on the Tianocore.org Web site include\r | |
128 | instructions for the use of Subversion Source Control.\r | |
129 | \r | |
130 | The URL of the EDK II repository is:\r | |
131 | https://edk2.tianocore.org/svn/edk2/trunk/edk2\r | |
132 | \r | |
133 | \r | |
134 | --------------------------------------------------------------------\r | |
135 | Notes On Required Tools (With examples for Windows, OS X, and Linux*)\r | |
136 | --------------------------------------------------------------------\r | |
137 | Software Installation Order:\r | |
138 | After installing the compiler tools and your Subversion client, install the\r | |
139 | following required tools in this order:\r | |
140 | 1. Java JDK\r | |
141 | 2. Apache-Ant\r | |
142 | 3. ant-contrib\r | |
143 | 4. xmlbeans\r | |
144 | 5. saxon8\r | |
145 | \r | |
146 | Java Development Kit:\r | |
147 | \r | |
148 | The Java Environment Variable must be set before attempting to build.\r | |
149 | For Sun JDK (see note below?:\r | |
150 | set JAVA_HOME=c:\Java\jdk1.5.0_06 (Windows example)\r | |
151 | export JAVA_HOME=/Library/Java/Home/ (OS X example)\r | |
152 | export JAVA_HOME=/usr/lib/j2sdk1.5-sun/ (Linux example)\r | |
153 | For Bea Systems:\r | |
154 | set JAVA_HOME=c:\Java\jrockit-R26.0.0-jdk1.5.0_04\r | |
155 | \r | |
156 | When using the Sun JDK5.0:\r | |
157 | During installation, you should specify the install directory as C:\Java\r | |
158 | instead of C:\Program Files\(or some other drive letter.) While installing\r | |
159 | to this non-standard location is not required, in practice, it seems to work\r | |
160 | more reliably.\r | |
161 | For the JDK, the install path is C:\Java\jdk1.5.0_06\r | |
162 | For the JRE, the install path is C:\Java\jre1.5.0_06\r | |
163 | Alternatively, you can specify C:\sunjavajdk and C:\sunjavajre.\r | |
164 | \r | |
165 | NOTE: You cannot combine the location for the JDK and the JRE, because the\r | |
166 | JRE install removes most of the binaries and libraries installed by the JDK\r | |
167 | install.\r | |
168 | \r | |
169 | Java Tools:\r | |
170 | The Apache-ANT requires the ANT_HOME environment variable to be set before\r | |
171 | attempting to build:\r | |
172 | set ANT_HOME=c:\<full path to where ant was installed>\r | |
173 | export ANT_HOME=~/ExternalTools/apache-ant (OS X and Linux example)\r | |
174 | \r | |
175 | The ant-contrib.jar file should be installed in the %ANT_HOME%\lib\r | |
176 | directory.\r | |
177 | \r | |
178 | XMLBeans, requires the XMLBEANS_HOME environment variable to be set\r | |
179 | before attempting to build:\r | |
180 | set XMLBEANS_HOME=C:\<full path to where xmlbeans was installed>\r | |
181 | export XMLBEANS_HOME=~/ExternalTools/xmlbeans (OS X and Linux example)\r | |
182 | \r | |
183 | Copy the saxon8.jar file to the %XMLBEANS_HOME%\lib directory.\r | |
184 | \r | |
185 | The Ant and XMLBean tools must be in the path.\r | |
186 | MS system example:\r | |
187 | set PATH=%PATH%;%ANT_HOME%\bin;%XMLBEANS_HOME%\bin\r | |
188 | Linux/OS X bash shell example:\r | |
189 | export PATH=$PATH:${ANT_HOME}/bin:${XMLBEANS_HOME}/bin\r | |
190 | \r | |
191 | --------------------\r | |
192 | A Word on Apache-ANT\r | |
193 | --------------------\r | |
194 | The Apache-ANT program is a build tool that uses XML-based project files.\r | |
195 | Similar to Makefiles, these project files may contain multiple targets. Most\r | |
196 | build.xml files in EDK II are auto-generated; any edits performed on the\r | |
197 | build.xml files will be overwritten by the next build.\r | |
198 | \r | |
199 | Pre-defined targets in the build.xml file include:\r | |
200 | all - This target builds binaries for defined architectures.\r | |
201 | clean - This target removes object files generated by commands.\r | |
202 | cleanall - This target removes all generated files and directories.\r | |
203 | \r | |
204 | Use the ANT option, -emacs, to remove the [cc] characters when an error occurs\r | |
205 | to provide a method for the Visual Studio IDE to open a file by double\r | |
206 | clicking the mouse on the file. Add -emacs to the end of the build command.\r | |
207 | ----------------------------\r | |
208 | A Word on the GCC Tool Chain\r | |
209 | ----------------------------\r | |
210 | \r | |
211 | EDK II will not compile with a standard Linux gcc tool chain. While Linux\r | |
212 | distributions are usually based on ELF, EDK II requires a version of gcc that\r | |
213 | is configured to produce PE-COFF images. You will find a script in <Root of\r | |
214 | EDK2 tree>/Tools/gcc/tianoCross-gcc-4.1 that will download, configure, compile,\r | |
215 | and install a gcc 4.1 cross-compile tool chain for EDK II development. This\r | |
216 | custom tool chain supports the IA-32 architecture. It can be built and run on\r | |
217 | Cygwin, Linux, and many other POSIX-compliant host operating environments. To\r | |
218 | compile the custom gcc tool chain, you need the following tools on your host\r | |
219 | computer: bash, gcc, gmake, curl (or wget).\r | |
220 | \r | |
221 | Only the OldMdePkg, EdkModulePkg and EdkUnixPkg are currently supported by gcc\r | |
222 | builds. Other builds, such as the EdkNt32Pkg, will not compile with gcc. By\r | |
223 | default, the edk2 will try to build the NT32.fpd, which is not supported by\r | |
224 | gcc. So, you need to change the Tools/Conf/target.txt.\r | |
225 | \r | |
226 | The cross-compile build script has been tested on Cygwin, OS X and Linux. You\r | |
227 | should expect to hack on these scripts to make them work on your system. You\r | |
228 | may need to install additional tools on your system to make the scripts work.\r | |
229 | \r | |
230 | You will need\r | |
231 | \r | |
232 | A recent version (3.0 or later should be fine) of gcc that is able to produce\r | |
233 | executables for the machine that you want to run this compiler on (the host\r | |
234 | machine).\r | |
235 | wget or curl (which enables the download of the gcc compiler source code)\r | |
236 | tar\r | |
237 | bzip\r | |
238 | gzip\r | |
239 | bash\r | |
240 | and possibly others\r | |
241 | \r | |
242 | CYGWIN Notes\r | |
243 | \r | |
244 | You should setup cygwin to use binmode on all mounts. When you initially\r | |
245 | install cygwin it gives you the choice of Unix file mode (recommended) or DOS\r | |
246 | file mode. Unix mode will cause all the cygwin directories to be mounted in\r | |
247 | binmode, while DOS will mount the dirs in textmode. Here is an example of a\r | |
248 | cygwin install where the dirs are (properly) mounted in binmode.\r | |
249 | To view mount information, type:\r | |
250 | mount\r | |
251 | \r | |
252 | C:\cygwin\bin on /usr/bin type user (binmode)\r | |
253 | C:\cygwin\lib on /usr/lib type user (binmode)\r | |
254 | c:\workspace on /workspace type system (binmode)\r | |
255 | C:\cygwin on / type user (binmode)\r | |
256 | \r | |
257 | If you use textmode, it is likely that the build will fail in a way that is\r | |
258 | hard to debug. Textmode is required to retain or add the DOS ^M characters\r | |
259 | in DOS batch files during file editing sessions.\r | |
260 | \r | |
261 | You can switch from textmode to binmode for compilation by executing the\r | |
262 | following:\r | |
263 | mount -b --change-cygdrive-prefix cygdrive\r | |
264 | \r | |
265 | Cygwin is pretty slow, so it is not recommended for large builds.\r | |
266 | \r | |
267 | \r | |
268 | \r | |
269 | \r | |
270 | \r | |
271 | The platform to be built is identified by the Tools/Conf/target.txt file:\r | |
272 | \r | |
273 | #\r | |
274 | # PROPERTY Type Use Description\r | |
275 | # ---------------- -------- -------- -----------------------------------------------------------\r | |
276 | # ACTIVE_PLATFORM Filename Recommended Specify the WORKSPACE relative Path and Filename\r | |
277 | # of the platform FPD file that will be used for the build\r | |
278 | # This line is required if and only if the current working\r | |
279 | # directory does not contain one or more FPD files.\r | |
280 | \r | |
281 | ACTIVE_PLATFORM =\r | |
282 | \r | |
283 | You can leave it black, as above, or set it to any .fpd file in the workspace.\r | |
284 | If you leave it blank, then you just cd to the dir that contains the .fpd that\r | |
285 | you would like to build (OldMdePkg/ or EdkModulePkg/) and then type build.\r | |
286 | \r | |
287 | ----------------------------\r | |
288 | A Word on compiling on Linux\r | |
289 | ----------------------------\r | |
290 | \r | |
291 | In order to compile on Linux, you will need to have the e2fsprogs-devel package\r | |
292 | installed. Check your distribution for the rpm, deb or other package format.\r | |
293 | This package contains the uuid library and header that are used by some of the\r | |
294 | host tools.\r | |
295 | \r | |
296 | If you are running on x86_64 Linux, then you should install a 64 bit version of\r | |
297 | the Java JDK. The version that was used was jdk-1_5_0_07-linux-amd64-rpm.bin.\r | |
298 | It may be downloaded from sun.com.\r | |
299 | \r | |
300 | -----------------------------------------\r | |
301 | A Word on compiling under Cygwin with gcc\r | |
302 | -----------------------------------------\r | |
303 | \r | |
304 | Cygwin is a POSIX style operating environment for Windows. It is possible to\r | |
305 | compile the EDK 2 using gcc and cygwin. Compiling under cygwin is slow, because\r | |
306 | the underlying file accesses are slow in cygwin. For this reason, we do not\r | |
307 | encourage the use of cygwin. A true unix system will be a superior choice for\r | |
308 | those wishing to compile with gcc.\r | |
309 | \r | |
310 | Make sure that you select the e2fsprogs development package when you install\r | |
311 | cygwin. It is necessary for the GenFvImage tool.\r | |
312 | \r | |
313 | ----------------------------------------\r | |
314 | A Word on gcc for Processor Architectures\r | |
315 | ----------------------------------------\r | |
316 | \r | |
317 | Currently gcc support is limited to IA-32 builds, generating IA-32 PE32 images.\r | |
318 | \r | |
319 | The X64 bit (Intel 64, etc.) support under the gcc compiler does not support the EFIAPI\r | |
320 | calling convention (as defined in the UEFI 2.0 specification Chapter 2), so it is not\r | |
321 | possible to build a working EFI image for an X64 environment. Since the x64 gcc does\r | |
322 | not support the EFIAPI calling convention the x64 tools do not support generating a\r | |
323 | PE32+ image. The EFIAPI calling convention is very similar to the Microsoft x64\r | |
324 | calling convention.\r | |
325 | \r | |
326 | We have added prelinary support for the MinGW64 Tool chain. This gcc tool\r | |
327 | chain is ported to follow the Microsft X64 ABI, and therefore is compatible\r | |
328 | with the EFI specification.\r | |
329 | \r | |
330 | On Itanium?Processors the gcc compiler does not support generating a PE32+ image.\r | |
331 | \r | |
332 | ----------------------------------------\r | |
333 | A Word on EdkUnixPkg -- The Unix simulator\r | |
334 | ----------------------------------------\r | |
335 | \r | |
336 | A unix port of the Nt32 simulator has been added to the project. It currently\r | |
337 | builds and runs on 32 bit Linux, but should be portable to other Unix\r | |
338 | variants. In order to build it, you should use the ELFGCC tool chain defintion\r | |
339 | in tools_def.txt, which is set in target.txt. These are two settings to make\r | |
340 | in Tools/Conf/target.txt:\r | |
341 | \r | |
342 | ACTIVE_PLATFORM = EdkUnixPkg/Unix.fpd\r | |
343 | TOOL_CHAIN_TAG = ELFGCC\r | |
344 | \r | |
345 | Once that is setup, type build, and then you will end up with the simulator in\r | |
346 | Build/Unix/DEBUG_ELFGCC/IA32/SecMain.exe.\r | |
347 | \r | |
348 | In order to use the gdb debugger with the simulator, you may need to load the\r | |
349 | correct symbol file for the various modules that are loaded. For example,\r | |
350 | \r | |
351 | add-symbol-file EdkModulePkg/Bus/Pci/PciBus/Dxe/PciBus/DEBUG/./PciBus.dll\r | |
352 | 0x45dc6000\r | |
353 | \r | |
354 | You can see the names of the symbol files (they are in ELF format even though\r | |
355 | the extension is .dll) printed on the screen as the simulator comes up.\r | |
356 | \r | |
357 | -----------------------\r | |
358 | Notes on Documentation\r | |
359 | -----------------------\r | |
360 | The documents are being managed by the Subversion Source Control on\r | |
361 | Tianocore.org. The document repository is "docs" and must be checked out\r | |
362 | separately from the EDK II source tree. Refer to the checkout procedures on\r | |
363 | the Tianocore.org Web site for EDK II.\r | |
364 | \r | |
365 | The URL of the document repository is:\r | |
366 | https://edk2.tianocore.org/svn/edk2/trunk/docs\r | |
367 | \r | |
368 | \r | |
369 | -------------------------------------------------------------------------------\r | |
370 | Quick Start\r | |
371 | -----------\r | |
372 | (assumes Microsoft Tools and OS environment, for GCC Tools or Linux, see\r | |
373 | "Detailed Starting Instructions" below)\r | |
374 | \r | |
375 | Follow the instructions at https://edk2.tianocore.org/servlets/ProjectSource to\r | |
376 | check out the entire EDK II source tree.\r | |
377 | \r | |
378 | In a command window, change to the top-level directory of the EDK II source.\r | |
379 | \r | |
380 | To test your tool chain setup and to build the supplied tools, execute:\r | |
381 | c:\MyWork\edk2\> edksetup ForceRebuild\r | |
382 | \r | |
383 | (The edksetup script is referred to as the setup command throughout the\r | |
384 | rest of this document.)\r | |
385 | NOTE: You should run the setup command at the start of every session.\r | |
386 | This configures the environment to include the TianoTools and the\r | |
387 | Java applications and libraries.\r | |
388 | \r | |
389 | You will need to set the WORKSPACE environment variable, or run the edksetup\r | |
390 | script (without any arguments), any time you want to build.\r | |
391 | \r | |
392 | Set the WORKSPACE environment variable, e.g.:\r | |
393 | \r | |
394 | c:\> set WORKSPACE=C:\MyWork\edk2\r | |
395 | \r | |
396 | You may need to edit the text files Tools/Conf/target.txt and\r | |
397 | Tools/Conf/tools_def.txt (created by edksetup) using your favorite\r | |
398 | text editor to ensure that the paths to the tools you want to use\r | |
399 | to build EDK II binaries are correct. These files contain the default\r | |
400 | paths (as per the default installation of the tools), so a customized\r | |
401 | install may require this manual process.\r | |
402 | \r | |
403 | Once this is completed, you are ready to test the build, by executing:\r | |
404 | c:\MyWork\edk2\> build\r | |
405 | \r | |
406 | This command builds the active platform specified in text file target.txt. If\r | |
407 | the active platform is not specified target.txt, you must execute the build\r | |
408 | command from the sub-directory that contains FPD files. For more information\r | |
409 | about the active platform policy, see the "EDK II Build and Packaging\r | |
410 | Architecture Specification."\r | |
411 | \r | |
412 | -------------------------------------------------------------------------------\r | |
413 | Detailed Starting Instructions\r | |
414 | ------------------------------\r | |
415 | \r | |
416 | Follow the instructions at https://edk2.tianocore.org/servlets/ProjectSource to\r | |
417 | check out the entire EDK II source tree.\r | |
418 | \r | |
419 | In a command window, change to the top-level directory of the EDK II source.\r | |
420 | \r | |
421 | If the active compiler tool chain is GCC, you must set the\r | |
422 | environment variable, TOOL_CHAIN to "gcc" before running the\r | |
423 | edksetup script. Example: export TOOL_CHAIN=gcc\r | |
424 | \r | |
425 | To test your tool chain setup and to build the supplied tools, execute:\r | |
426 | c:\MyWork\edk2\> edksetup ForceRebuild\r | |
427 | \r | |
428 | On Linux systems, you must source the edksetup.sh file to load the correct\r | |
429 | settings into your shell.\r | |
430 | \r | |
431 | . edksetup.sh # Note the dot.\r | |
432 | \r | |
433 | If you have recently updated your code from subversion, the tools will need to\r | |
434 | be rebuilt if there were any code changes made to them. You can request that\r | |
435 | the tools get rebuilt by typing:\r | |
436 | \r | |
437 | . edksetup.sh Rebuild # Unix-like systems\r | |
438 | edksetup.bat Rebuild # Windows\r | |
439 | \r | |
440 | The edksetup script is referred to as the setup command throughout the\r | |
441 | rest of this document.\r | |
442 | NOTE: You should run the setup command (edksetup)at the start of every\r | |
443 | session. This configures the environment to include the\r | |
444 | TianoTools and the Java applications and libraries.\r | |
445 | \r | |
446 | Any changes to the tool source code or XML Schema documents require that\r | |
447 | you execute the following:\r | |
448 | c:\MyWork\edk2\> edksetup ForceRebuild\r | |
449 | \r | |
450 | You must set the WORKSPACE environment variable, or run the edksetup\r | |
451 | script (without any arguments), any time you want to build.\r | |
452 | \r | |
453 | Set the WORKSPACE environment variable, e.g.:\r | |
454 | \r | |
455 | c:\> set WORKSPACE=C:\MyWork\edk2\r | |
456 | \r | |
457 | You may need to edit the text files Tools/Conf/target.txt and\r | |
458 | Tools/Conf/tools_def.txt (created by edksetup) using your favorite\r | |
459 | text editor to ensure that the paths to the tools you want to use\r | |
460 | to build EDK II binaries are correct. These files contain the default\r | |
461 | paths (as per the default installation of the tools), so a customized\r | |
462 | tool installation may require this manual process.\r | |
463 | \r | |
464 | Once this is completed, you are ready to test the build, by executing:\r | |
465 | c:\MyWork\edk2\> build\r | |
466 | \r | |
467 | This command builds the active platform specified in text file target.txt. If\r | |
468 | the active platform is not specified, go to the sub-directory that contains FPD\r | |
469 | files and execute the build command. For more information about the active\r | |
470 | platform policy, see the "EDK II Build and Packaging Architecture\r | |
471 | Specification."\r | |
472 | \r | |
473 | --------------------------\r | |
474 | Individual Platform Builds\r | |
475 | --------------------------\r | |
476 | After running the setup command, you can build individual platforms.\r | |
477 | In the command window:\r | |
478 | Set the active platform in target.txt, and execute this command:\r | |
479 | c:\<directory>\> build\r | |
480 | or\r | |
481 | cd to the platform (FPD file) that you want to build and execute this command:\r | |
482 | c:\MyWork\edk2\EdkNt32Pkg\> build\r | |
483 | \r | |
484 | Note that the active platform specified in target.txt overrides the platform\r | |
485 | specified by any FPD file in the current directory. For more information\r | |
486 | about active platform policy, see the "EDK II Build and Packaging Architecture\r | |
487 | Specification."\r | |
488 | \r | |
489 | To run the Nt32 emulation platform under Microsoft Windows, go to\r | |
490 | <full build path>\DEBUG\MSFT\IA32 and execute SecMain.exe\r | |
491 | \r | |
492 | To exit the Nt32 emulation platform, type "reset" at the EFI Shell>\r | |
493 | command prompt. Alternatively, from the graphical interface, select the Boot\r | |
494 | Maintenance Manager's "Reset System" command.\r | |
495 | \r | |
496 | NOTE: When creating a new platform, the Platform Name is restricted\r | |
497 | to a single word containing alphanumeric characters, underscore, dash,\r | |
498 | and period. The space character and other special characters are\r | |
499 | not allowed.\r | |
500 | \r | |
501 | -----------------------\r | |
502 | Notes on Symbolic Debug\r | |
503 | -----------------------\r | |
504 | To enable EFI Symbolic Debugging, make sure the target output is set to DEBUG\r | |
505 | in the text file Tools/Conf/target.txt and then modify the FPD <BuildOptions>\r | |
506 | <Options><Option BuildTargets="DEBUG" ToolCode="CC"> and append the following\r | |
507 | compiler options to the string:\r | |
508 | "/D EFI_GENERATE_SYM_FILE", "/D EFI_SYMBOLIC_DEBUG"\r | |
509 | \r | |
510 | (If the Option line does not contain "/D EFI_DEBUG", you must add that\r | |
511 | option as well.)\r | |
512 | \r | |
513 | ------------------------\r | |
514 | Individual Module Builds\r | |
515 | ------------------------\r | |
516 | After running the setup command, you can build individual modules.\r | |
517 | In the command window, cd to the module that you want to build, and\r | |
518 | execute the build command:\r | |
519 | c:\MyWork\edk2\OldMdePkg\Library\BaseLib\> build\r | |
520 | \r | |
521 | You must set the active platform in target.txt for individual module builds.\r | |
522 | \r | |
523 | -------------------------------------------------------------------------------\r | |
524 | \r | |
525 | General Information:\r | |
526 | ===============================================================\r | |
527 | Mechanisms\r | |
528 | ----------\r | |
529 | A brief overview:\r | |
530 | \r | |
531 | A) The Surface Area Package Description (SPD) file contains information about\r | |
532 | the modules that the package contains, including the location of all MSA files,\r | |
533 | and public library names and headers that might be provided by a module in the\r | |
534 | package. Packages are defined by SPD files. (Found in the root of the Package\r | |
535 | subdirectory (i.e. EdkNt32Pkg).) The SPD file is further explained in "EDK II\r | |
536 | Build and Packaging Architecture Specification."\r | |
537 | \r | |
538 | B) Module Surface Area Definition (MSA) files. A description of a module's\r | |
539 | surface area, with all module specific default flags and features specified.\r | |
540 | For additional details, see the "EDK II Module Surface Area Specification" and\r | |
541 | the "EDK II Build and Packaging Architecture Specification."\r | |
542 | \r | |
543 | C) Framework Platform Description (FPD) files. A description of a platform's\r | |
544 | surface are, including a list of modules that are needed by the platform. To\r | |
545 | support individual module builds, developers are not required to provide\r | |
546 | information about specific flash devices, nor flash device layout.\r | |
547 | Specific sections in the FPD file control aspects of the build, such\r | |
548 | as the Supported Architectures and Build Targets, as well as the tool flags\r | |
549 | that are used to create the binary files. A valid platform file can specify\r | |
550 | zero or more modules, so individual modules can be compiled within the context\r | |
551 | of a platform (FPD) definition.\r | |
552 | \r | |
553 | D) Platform Configuration Database (PCD). A platform database that contains a\r | |
554 | variety of current platform settings or directives that can be accessed by a\r | |
555 | driver or application. The PCD is defined by the PCD_Protocol (This is\r | |
556 | further explained in the "EDK II Platform Configuration Database Infrastructure\r | |
557 | Description."\r | |
558 | \r | |
559 | E) Library Class. A library class is a logical grouping of similar functions.\r | |
560 | When developing components, the module surface area declares the class of\r | |
561 | libraries that can be used by the component. The MSA and SPD files can specify\r | |
562 | a recommended instance of the library that a platform integrator (PI) may\r | |
563 | select, however this is only a recommendation. The PI may choose to select a\r | |
564 | different library instance to be used during compilation and linking. All\r | |
565 | library type modules must include header files in their distribution package,\r | |
566 | as well as their MSA files. Components, on the other hand, need provide only an\r | |
567 | MSA file and either source or binary files when distributing packages. The\r | |
568 | Library Classes are further explained in the "EDK II Build and Packaging\r | |
569 | Architecture Specification."\r | |
570 | \r | |
571 | =========================================================================\r | |
572 | The common operations by developers of new modules are:\r | |
573 | -----------------------------------------------\r | |
574 | 1) Manually creating a new module in a package:\r | |
575 | - The module source code must first be created in an appropriate directory\r | |
576 | (under the package the module is to be a part of.)\r | |
577 | - An MSA file must be created, spelling out all aspects of the module.\r | |
578 | - The MSA must be added to the SPD for the package to include the module.\r | |
579 | \r | |
580 | -----------------------------------------------------\r | |
581 | 2) Adding and Removing modules to and from a package:\r | |
582 | \r | |
583 | - Set up environment as Build\r | |
584 | - Adding a module to a package:\r | |
585 | - Generate the MSA file\r | |
586 | - Add a new <Filename> element under <MsaFiles> into\r | |
587 | <PackageDir>\<PackageName>.spd, using arelative path to the package\r | |
588 | - Add a new <ModuleSA> entry under each <FrameworkModules> into the\r | |
589 | <PackageDir>\<PackageName>.fpd file if necessary.\r | |
590 | \r | |
591 | - Removing a module from a package:\r | |
592 | - Comment out or remove the corresponding <Filename> element under\r | |
593 | <MsaFiles> from <PackageDir>\<PackageName>.spd\r | |
594 | - Comment out or remove the corresponding <ModuleSA> entry under each\r | |
595 | <FrameworkModules> from <PackageDir>\<PackageName>.fpd if necessary.\r | |
596 | \r | |
597 | -------------------------------\r | |
598 | 3) Manually creating a package:\r | |
599 | - Identify the modules that are to be members of the project.\r | |
600 | - Identify the Variables and Guids required in and of the Package (including\r | |
601 | consumption and production information).\r | |
602 | - Create an SPD file defining these modules and calling out their MSA files.\r | |
603 | - Add a new <Filename> element under <PackageList> into\r | |
604 | Tools\Conf\FrameworkDatabase.db, using the relative path to the workspace.\r | |
605 | \r | |
606 | -----------------------------------------\r | |
607 | 4) Declaring a new Protocol in a package:\r | |
608 | - This release requires manual editing of the SPD file, adding the protocol\r | |
609 | to the ProtocolDeclarations section of the file.\r | |
610 | - Add the Protocol .h file to the Include\Protocol directory.\r | |
611 | - Add an <Entry> to the <ProtocolDeclarations> element in the\r | |
612 | <PackageName>.spd file\r | |
613 | - Each line contains Protocol base name, followed by the global variable\r | |
614 | name, and the hex value of the Protocol GUID.\r | |
615 | \r | |
616 | Example Protocol Entries (NOTE: The Guid entry is a single line in the SPD\r | |
617 | file):\r | |
618 | <ProtocolDeclarations>\r | |
619 | <Entry Name="Bds">\r | |
620 | <C_Name>gEfiBdsArchProtocolGuid</C_Name>\r | |
621 | <GuidValue>665E3FF6-46CC-11D4-9A38-0090273FC14D</GuidValue>\r | |
622 | <HelpText/>\r | |
623 | </Entry>\r | |
624 | <Entry Name="Cpu">\r | |
625 | <C_Name>gEfiCpuArchProtocolGuid</C_Name>\r | |
626 | <GuidValue>26BACCB1-6F42-11D4-BCE7-0080C73C8881</GuidValue>\r | |
627 | <HelpText/>\r | |
628 | </Entry>\r | |
629 | </ProtocolDeclarations>\r | |
630 | \r | |
631 | ------------------------------------\r | |
632 | 5) Declaring a new PPI in a package:\r | |
633 | - This release requires manual editing of the SPD file\r | |
634 | - Add the PPI .h file to the Include\Ppi directory.\r | |
635 | - Add an <Entry> to the package <PpiDeclarations> element in the\r | |
636 | <PackageName>.spd file\r | |
637 | - Each line contains the PPI base name, followed by the global variable\r | |
638 | name and the hex value of the PPI GUID.\r | |
639 | \r | |
640 | Example Ppi Entries (NOTE: The Guid entry is a single line in the SPD file):\r | |
641 | <PpiDeclarations>\r | |
642 | <Entry Name="BootInRecoveryMode">\r | |
643 | <C_Name>gEfiPeiBootInRecoveryModePpiGuid</C_Name>\r | |
644 | <GuidValue>17EE496A-D8E4-4B9A-94D1-CE8272300850</GuidValue>\r | |
645 | <HelpText/>\r | |
646 | </Entry>\r | |
647 | <Entry Name="CpuIo">\r | |
648 | <C_Name>gEfiPeiCpuIoPpiInServiceTableGuid</C_Name>\r | |
649 | <GuidValue>E6AF1F7B-FC3F-46DA-A828-A3B457A44282</GuidValue>\r | |
650 | <HelpText/>\r | |
651 | </Entry>\r | |
652 | </PpiDeclarations>\r | |
653 | \r | |
654 | -------------------------------------\r | |
655 | 6) Declaring a new GUID in a package:\r | |
656 | - This release requires manual editing of the SPD file to include the new\r | |
657 | Guid. This is identical to adding a ProtocolDeclaration or PpiDeclaration\r | |
658 | element, as described above.\r | |
659 | \r | |
660 | ------------------------------------------\r | |
661 | 7) Declaring a new PCD entry in a package:\r | |
662 | - This release requires manual editing of the SPD file to include the new\r | |
663 | PCD. New Pcd entries are added to the PcdDefinitions section of the\r | |
664 | <PackageName>.spd file using the following example for the format\r | |
665 | (NOTE: The hex <Token> value must be unique):\r | |
666 | \r | |
667 | <PcdDeclarations>\r | |
668 | <PcdEntry ItemType="FIXED_AT_BUILD">\r | |
669 | <C_Name>PcdMaximumUnicodeStringLength</C_Name>\r | |
670 | <Token>0x00000001</Token>\r | |
671 | <TokenSpaceGuidCName>gEfiMdePkgTokenSpaceGuid</TokenSpaceGuidCName>\r | |
672 | <DatumType>UINT32</DatumType>\r | |
673 | <ValidUsage>FIXED_AT_BUILD</ValidUsage>\r | |
674 | <DefaultValue>1000000</DefaultValue>\r | |
675 | <HelpText>The maximum lengh for unicode string.</HelpText>\r | |
676 | </PcdEntry>\r | |
677 | </PcdDeclarations>\r | |
678 | \r | |
679 | ------------------------------\r | |
680 | 8) Declaring a new Library Class:\r | |
681 | - This release requires manual editing of the SPD file to include the new\r | |
682 | Library Class. New Library Class entries are added to the\r | |
683 | LibraryClassDeclarations section of the <PackageName>.spd file using\r | |
684 | the following example for the format:\r | |
685 | \r | |
686 | <LibraryClassDeclarations>\r | |
687 | <LibraryClass Name="BaseLib">\r | |
688 | <IncludeHeader>Include/Library/BaseLib.h</IncludeHeader>\r | |
689 | <HelpText/>\r | |
690 | </LibraryClass>\r | |
691 | <LibraryClass Name="BaseMemoryLib">\r | |
692 | <IncludeHeader>Include/Library/BaseMemoryLib.h</IncludeHeader>\r | |
693 | <HelpText/>\r | |
694 | </LibraryClass>\r | |
695 | </LibraryClassDeclarations>\r | |
696 | \r | |
697 | =======================================================\r | |
698 | EDK II Changes Relative to the original EDK:\r | |
699 | --------------------------------------------\r | |
700 | The EDK II represents significant changes in the structure of the EDK.\r | |
701 | Therefore, it is very difficult to isolate all of the changes of this version of\r | |
702 | the EDK with the original EDK.\r | |
703 | \r | |
704 | Of particular note:\r | |
705 | \r | |
706 | 1) EDK II contains new hardware feature support for the ICH SMBUS Libraries.\r | |
707 | These libraries are provided to make Memory Reference Code (MRC) development\r | |
708 | easier.\r | |
709 | 2) The MDE libraries represent significant changes in source\r | |
710 | (with only limited changes in functionality.) These new libraries conform\r | |
711 | to the "EDK II Module Development Environment Library Specification.?\r | |
712 | 3) The Fat Binary and the EDK Shell Binary Packages are functionally identical\r | |
713 | to the original EDK.\r | |
714 | 4) The EDK tools directory has been expanded to include more tools and more\r | |
715 | tool functionality.\r | |
716 | 5) The EDK NT32 section has been ported to the new build process, but\r | |
717 | functionally remains the same as the original EDK.\r | |
718 | 6) The Application "HelloWorld" has been ported to EDK II as well.\r | |
719 | \r | |
720 | =======================================================\r | |
721 | Virus scanned by McAfee VirusScan Enterprise 8.0.0, Virus Definitions 4890, no\r | |
722 | virus detected.\r | |
723 | \r | |
724 | vim:tw=78:ts=2:com=fb\:- :ai\r |