supplemented "/FI" to some ignored PP options in fpd files

[mirror_edk2.git] / ReleaseNotes.txt

diff --git a/ReleaseNotes.txt b/ReleaseNotes.txt
index b59f5a36169acca479dd6af09be13a634f57114b..1214078894567deac8010ab488e160ded9b8a1f5 100644 (file)
--- a/ReleaseNotes.txt
+++ b/ReleaseNotes.txt
@@ -48,7 +48,7 @@ prior to using the Edk 2.0.
 Compiler Tool Chain\r
       Microsoft* Visual Studio .NET 2003*  (http://www.microsoft.com)\r
     or\r
-      GCC version 4.x or later (http://gcc.gnu.org)\r
+      A special GCC version 4.x or later (http://gcc.gnu.org). See below.\r
 \r
 Assembler Tool Chain\r
       Microsoft Macro Assembler, version 6.15 or later\r
@@ -188,6 +188,25 @@ Once this is completed, you are ready to test the Build, by executing:
 \r
 This command builds all of the packages, including the NT32 reference platform.\r
 \r
+------------------------------------\r
+Build Architectures other than IA32.\r
+------------------------------------\r
+\r
+By default, we are set up to build the ia32 architecture. If you would like to\r
+build for IPF, x64 and EBC, please copy MdePkg/MdePkg-All-Arch.fpd to\r
+MdePkg/MdePkg.fpd. For EdkModulePkg, copy EdkModulePkg-All-Archs.fpd to\r
+EdkModulePkg.fpd. Note, you may also add only the architecture you want from\r
+the -All-Archs files to the main fpd file. This is preferred if you do not have\r
+all the compilers installed.\r
+\r
+Optionally, you may modify the path to the compiler in\r
+Tools/Conf/msft_tools_def.txt. The flags for the ARCH tool chain are set in the\r
+file names by Tools/Conf/VENDOR_tools.txt, where VENDOR is set in\r
+Tools/Conf/msft_tools.txt.\r
+\r
+For example, if IPF_VENDOR = WINDDK, then the flags for the IPF DDK compiler\r
+will be specified in Tools/Conf/winddk_tools.txt.\r
+\r
 -------------------------\r
 Individual Package Builds\r
 -------------------------\r
@@ -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\r
 platform under Microsoft Windows.\r
 \r
+To exit the Nt32 emulation platform, you may type reset at the EFI Shell>\r
+command prompt.  Alternately, you may use the Graphical interface, Boot\r
+Maintenance Manager screen's Reset System command.\r
+\r
 ------------------------\r
 Individual Module Builds\r
 ------------------------\r
@@ -222,12 +245,15 @@ Pre-defined targets in the build.xml files include:
 \r
 A Word on GCC tool chain\r
 ------------------------\r
-You will find a script in the tree that will download, configure, compile, and\r
-install a gcc 4.0.2 tool chain for development. It has support for the ia32\r
-architecture.  It can be built and run on Cygwin, Linux, and many other POSIX\r
-compliant host environments. There are a few tools that you will need on your\r
-host computer in order to compile the tool chain. Among them are bash, gcc,\r
-gmake, curl (or wget).\r
+EDK2 will not compile with a standard Linux gcc tool chain. While Linux\r
+distributions are usually based on ELF, EDK2 requires a version of gcc that is\r
+configured to produce PE-COFF images. You will find a script in edk2/Tools/gcc\r
+that will download, configure, compile, and install a gcc 4.X cross-compile\r
+tool chain for EDK2 development. It has support for the ia32 architecture. It\r
+can be built and run on Cygwin, Linux, and many other POSIX compliant host\r
+operating environments. There are a few tools that you will need on your host\r
+computer in order to compile the tool chain. Among them are bash, gcc, gmake,\r
+curl (or wget).\r
 \r
 -------------------------------------------------------------------------------\r
 \r