Fix the bug of library instance selection interference between different archs of...

[mirror_edk2.git] / ReleaseNotes.txt

diff --git a/ReleaseNotes.txt b/ReleaseNotes.txt
index d10f1efd0193c5dbe39afcb32d22a7e595c799c6..d3b5a719a9632443343acef3226dbb48b6de6e40 100644 (file)
--- a/ReleaseNotes.txt
+++ b/ReleaseNotes.txt
@@ -193,7 +193,25 @@ gcc tool chain, you need the following tools on your host computer: bash, gcc,
 gmake, curl (or wget).\r
 \r
 Only the MdePkg and EdkModulePkg are currently supported by gcc builds. Other\r
-builds, such as the EdkNt32Pkg, will not compile with gcc.\r
+builds, such as the EdkNt32Pkg, will not compile with gcc. By default, the edk2\r
+will try to build the NT32.fpd, which is not supported by gcc. So, you need to\r
+change the Tools/Conf/target.txt.\r
+\r
+The platform to be built is identified by the Tools/Conf/target.txt file:\r
+\r
+#\r
+#  PROPERTY              Type       Use         Description\r
+#  ----------------      --------   --------    -----------------------------------------------------------\r
+#  ACTIVE_PLATFORM       Filename   Recommended Specify the WORKSPACE relative Path and Filename \r
+#                                               of the platform FPD file that will be used for the build\r
+#                                               This line is required if and only if the current working\r
+#                                               directory does not contain one or more FPD files.\r
+\r
+ACTIVE_PLATFORM       =\r
+ \r
+You can leave it black, as above, or set it to any .fpd file in the workspace.\r
+If you leave it blank, then you just cd to the dir that contains the .fpd that\r
+you would like to build (MdePkg/ or EdkModulePkg/) and then type build.\r
 \r
 ----------------------------\r
 A Word on compiling on Linux\r
@@ -252,7 +270,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
@@ -297,13 +315,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
@@ -312,7 +337,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