X-Git-Url: https://git.proxmox.com/?p=mirror_edk2.git;a=blobdiff_plain;f=ReleaseNotes.txt;h=1214078894567deac8010ab488e160ded9b8a1f5;hp=48dc75e2828a04ac5944819b5b095597ddc47ec8;hb=90f7b6a81b96a112f196ff80e7cade4f951264a1;hpb=54a1ec66eb53509d47c5fbdbffc34a9ae7d15dd8

diff --git a/ReleaseNotes.txt b/ReleaseNotes.txt
index 48dc75e282..1214078894 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
 
@@ -185,6 +188,25 @@ Once this is completed, you are ready to test the Build, by executing:
 
 This command builds all of the packages, including the NT32 reference platform.
 
+------------------------------------
+Build Architectures other than IA32.
+------------------------------------
+
+By default, we are set up to build the ia32 architecture. If you would like to
+build for IPF, x64 and EBC, please copy MdePkg/MdePkg-All-Arch.fpd to
+MdePkg/MdePkg.fpd. For EdkModulePkg, copy EdkModulePkg-All-Archs.fpd to
+EdkModulePkg.fpd. Note, you may also add only the architecture you want from
+the -All-Archs files to the main fpd file. This is preferred if you do not have
+all the compilers installed.
+
+Optionally, you may modify the path to the compiler in
+Tools/Conf/msft_tools_def.txt. The flags for the ARCH tool chain are set in the
+file names by Tools/Conf/VENDOR_tools.txt, where VENDOR is set in
+Tools/Conf/msft_tools.txt.
+
+For example, if IPF_VENDOR = WINDDK, then the flags for the IPF DDK compiler
+will be specified in Tools/Conf/winddk_tools.txt.
+
 -------------------------
 Individual Package Builds
 -------------------------
@@ -196,6 +218,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 +245,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 +261,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