X-Git-Url: https://git.proxmox.com/?p=mirror_edk2.git;a=blobdiff_plain;f=ReleaseNotes.txt;h=1214078894567deac8010ab488e160ded9b8a1f5;hp=b59f5a36169acca479dd6af09be13a634f57114b;hb=3f6001d4f0ecb1125de48690655a1c3aba3f37e7;hpb=8fb9e6b8a1806d6c95a1038421e7ec6686ef47d6

diff --git a/ReleaseNotes.txt b/ReleaseNotes.txt
index b59f5a3616..1214078894 100644
--- a/ReleaseNotes.txt
+++ b/ReleaseNotes.txt
@@ -48,7 +48,7 @@ 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
@@ -188,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
 -------------------------
@@ -199,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
 ------------------------
@@ -222,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).
 
 -------------------------------------------------------------------------------