Remove additional / or \ in relative path.

[mirror_edk2.git] / ReleaseNotes.txt

diff --git a/ReleaseNotes.txt b/ReleaseNotes.txt
index de392458bb5187e4ff494ab88ebf95a9a90e3104..d3b5a719a9632443343acef3226dbb48b6de6e40 100644 (file)
--- a/ReleaseNotes.txt
+++ b/ReleaseNotes.txt
@@ -270,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
 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
 \r
 (The edksetup script is referred to as the setup command throughout the \r
 rest of this document.)\r


@@ -315,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
 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
 \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
 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 +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
 \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
 \r
 You must set the WORKSPACE environment variable, or run the edksetup\r
 script (without any arguments), any time you want to build.\r