Added target Wizard which just relies on the SurfaceArea. Also fixed the echo messages.

[mirror_edk2.git] / ReleaseNotes.txt

diff --git a/ReleaseNotes.txt b/ReleaseNotes.txt
index de392458bb5187e4ff494ab88ebf95a9a90e3104..b9da6c308069e353e7c97f51ac34e6826fc211b9 100644 (file)
--- a/ReleaseNotes.txt
+++ b/ReleaseNotes.txt
@@ -246,6 +246,16 @@ system will be a superior choice for those wishing to compile with gcc.
 Make sure that you select the e2fsprogs development package when you install\r
 cygwin. It is necessary for the GenFvImage tool.\r
 \r
+----------------------------------------\r
+A Word on gcc for Processor Architectures\r
+----------------------------------------\r
+\r
+Currently gcc support is limited to IA-32 builds, generating IA-32 PE32 images. \r
+\r
+The X64 bit (Intel 64, etc.) support under the gcc compiler does not support the EFIAPI calling convention (as defined in the UEFI 2.0 specification Chapter 2), so it is not possible to build a working EFI image for an X64 environment.  Since the x64 gcc does not support the EFIAPI calling convention the x64 tools do not support generating a PE32+ image.  The EFIAPI calling convention is very similar to the Microsoft x64 calling convention.\r
+\r
+On Itanium® Processors the gcc compiler does not support generating a PE32+ image.\r
+\r
 -----------------------\r
 Notes on Documentation\r
 -----------------------\r
@@ -270,7 +280,7 @@ check out the entire EDK II source tree.
 In a command window, change to the top-level directory of the EDK II source.\r
 \r
 To test your tool chain setup and to build the supplied tools, execute:\r
-    c:\MyWork\edkii\> edksetup ForceBuild\r
+    c:\MyWork\edkii\> edksetup ForceRebuild\r
 \r
 (The edksetup script is referred to as the setup command throughout the \r
 rest of this document.)\r
@@ -315,13 +325,20 @@ environment variable, TOOL_CHAIN to "gcc" before running the
 edksetup script.  Example: export TOOL_CHAIN=gcc\r
 \r
 To test your tool chain setup and to build the supplied tools, execute:\r
-    c:\MyWork\edkii\> edksetup ForceBuild\r
+    c:\MyWork\edkii\> edksetup ForceRebuild\r
 \r
 On Linux systems, you must source the edksetup.sh file to load the correct\r
 settings into your shell.\r
 \r
     . edksetup.sh # Note the dot.\r
 \r
+If you have recently updated your code from subversion, the tools will need to\r
+be rebuilt if there were any code changes made to them. You can request that\r
+the tools get rebuilt by typing:\r
+\r
+    . edksetup.sh Rebuild # Unix-like systems\r
+    edksetup.bat Rebuild  # Windows\r
+\r
 The edksetup script is referred to as the setup command throughout the \r
 rest of this document.\r
       NOTE: You should run the setup command at the start of every session.\r
@@ -330,7 +347,7 @@ rest of this document.
 \r
 Any changes to the tool source code or XML Schema documents require that\r
 you execute the following:\r
-   c:\MyWork\edkii\> edksetup ForceBuild\r
+   c:\MyWork\edkii\> edksetup ForceRebuild\r
 \r
 You must set the WORKSPACE environment variable, or run the edksetup\r
 script (without any arguments), any time you want to build.\r