X-Git-Url: https://git.proxmox.com/?p=mirror_edk2.git;a=blobdiff_plain;f=ReleaseNotes.txt;h=6e2ac02ced87a96321e5f05f0df9b2c3575fd6fb;hp=48dc75e2828a04ac5944819b5b095597ddc47ec8;hb=6c4dc2267a9c87d40ff6bfc042e13b3e838df26e;hpb=54a1ec66eb53509d47c5fbdbffc34a9ae7d15dd8 diff --git a/ReleaseNotes.txt b/ReleaseNotes.txt index 48dc75e282..6e2ac02ced 100644 --- a/ReleaseNotes.txt +++ b/ReleaseNotes.txt @@ -48,12 +48,12 @@ prior to using the Edk 2.0. Compiler Tool Chain Microsoft* Visual Studio .NET 2003* (http://www.microsoft.com) or - GCC version 4.x or later (http://gcc.gnu.org) + A special GCC version 4.x or later (http://gcc.gnu.org). See below. Assembler Tool Chain Microsoft Macro Assembler, version 6.15 or later or - GCC version 4.x or later + GNU binutils 2.16.1 or later Java Development Kit ( Java 5.0 or later) Sun* jdk-1.5.0_04 or later (http://java.sun.com) @@ -62,7 +62,8 @@ Java Development Kit ( Java 5.0 or later) Java Tools Apache-ANT, version 1.6.5 or later (http://ant.apache.org) - Ant-contrib, version 1.0b2 or later (http://antcontrib.sourceforge.net) + Ant-contrib, version 1.0b2 or later + (http://sourceforge.net/project/showfiles.php?group_id=36177) Saxon8, version 8.1.1 (http://prdownloads.sourceforge.net/saxon/saxonb8-1-1.zip?download) XMLBeans, version 2.1.0 or later (http://xmlbeans.apache.org) @@ -73,9 +74,11 @@ Other Tools Optional Tools -------------- Compiler Tool Chains: - Intel C++ Compiler for Windows, ver. 9.0 or later (http://www.intel,com) - Intel C Compiler for EFI Byte Code, ver. 1.2 or later + Intel C++ Compiler for Windows, ver. 9.0 or later (http://www.intel.com) + Intel C Compiler for EFI Byte Code, ver. 1.2 or later + (http://www.intel.com/cd/software/products/asmo-na/eng/compilers/efibc/index.htm) Microsoft Driver Development Kit, version 3790.1830 or later + (http://www.microsoft.com/whdc/devtools/ddk/orderddkcd.mspx) Microsoft ACPI Source Language Assembler, Version 1.0.13NT or later Intel ACPI Component Architecture, version 20060113 @@ -196,6 +199,10 @@ After running the setup command, you can build individual packages. The EdkNt32Pkg has a special target; "run" that will execute the Nt32 emulation platform under Microsoft Windows. +To exit the Nt32 emulation platform, you may type reset at the EFI Shell> +command prompt. Alternately, you may use the Graphical interface, Boot +Maintenance Manager screen's Reset System command. + ------------------------ Individual Module Builds ------------------------ @@ -219,12 +226,15 @@ Pre-defined targets in the build.xml files include: A Word on GCC tool chain ------------------------ -You will find a script in the tree that will download, configure, compile, and -install a gcc 4.0.2 tool chain for development. It has support for the ia32 -architecture. It can be built and run on Cygwin, Linux, and many other POSIX -compliant host environments. There are a few tools that you will need on your -host computer in order to compile the tool chain. Among them are bash, gcc, -gmake, curl (or wget). +EDK2 will not compile with a standard Linux gcc tool chain. While Linux +distributions are usually based on ELF, EDK2 requires a version of gcc that is +configured to produce PE-COFF images. You will find a script in edk2/Tools/gcc +that will download, configure, compile, and install a gcc 4.X cross-compile +tool chain for EDK2 development. It has support for the ia32 architecture. It +can be built and run on Cygwin, Linux, and many other POSIX compliant host +operating environments. There are a few tools that you will need on your host +computer in order to compile the tool chain. Among them are bash, gcc, gmake, +curl (or wget). ------------------------------------------------------------------------------- @@ -232,7 +242,7 @@ General Information: =============================================================== Mechanisms: ---------- -A quick understanding: +A brief overview: A) Surface Area Package Description (SPD) file contains information about the modules that the package contains, including the location of all MSA files, and