Updated ReleaseNotes.txt since the issue of build CompressDll.dll in cygwin is fixed...

[mirror_edk2.git] / ReleaseNotes.txt

diff --git a/ReleaseNotes.txt b/ReleaseNotes.txt
index b9da6c308069e353e7c97f51ac34e6826fc211b9..b965615797d07673daed72146a609b9b614f4c76 100644 (file)
--- a/ReleaseNotes.txt
+++ b/ReleaseNotes.txt
@@ -232,13 +232,7 @@ A Word on compiling under Cygwin with gcc
 \r
 Cygwin is a POSIX style operating environment for Windows. It is possible to\r
 compile the EDK 2 using gcc and cygwin. There are a few extra steps necessary\r
-to make this happen. There is a JNI (Java Native Interface) library in the\r
-Tools.  In order to compile this under Cygwin, the 'linux' java headers must be\r
-installed to the $JAVA_HOME dir on the windows system. To accomplish this, you\r
-must install the JDK on a linux system, and then copy\r
-linux:$JAVA_HOME/include/linux/ to windows:$JAVA_HOME/include. These are really\r
-typedefs needed by gcc.\r
-\r
+to make this happen. \r
 Compiling under cygwin is slow, because the underlying file accesses are slow\r
 in cygwin. For this reason, we do not encourage the use of cygwin. A true unix\r
 system will be a superior choice for those wishing to compile with gcc.\r
@@ -280,7 +274,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 ForceRebuild\r
+    c:\MyWork\edk2\> edksetup ForceRebuild\r
 \r
 (The edksetup script is referred to as the setup command throughout the \r
 rest of this document.)\r
@@ -293,7 +287,7 @@ script (without any arguments), any time you want to build.
 \r
   Set the WORKSPACE environment variable, e.g.:\r
 \r
-    c:\> set WORKSPACE=C:\MyWork\edkii\r
+    c:\> set WORKSPACE=C:\MyWork\edk2\r
 \r
 You may need to edit the text files Tools/Conf/target.txt and\r
 Tools/Conf/tools_def.txt (created by edksetup) using your favorite \r
@@ -303,7 +297,7 @@ paths (as per the default installation of the tools), so a customized
 install may require this manual process.\r
 \r
 Once this is completed, you are ready to test the build, by executing:\r
-    c:\MyWork\edkii\> build\r
+    c:\MyWork\edk2\> build\r
 \r
 This command builds the active platform specified in text file target.txt. If \r
 the active platform is not specified target.txt, you must execute the build \r
@@ -325,7 +319,7 @@ 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 ForceRebuild\r
+    c:\MyWork\edk2\> edksetup ForceRebuild\r
 \r
 On Linux systems, you must source the edksetup.sh file to load the correct\r
 settings into your shell.\r
@@ -347,14 +341,14 @@ 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 ForceRebuild\r
+   c:\MyWork\edk2\> 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
   Set the WORKSPACE environment variable, e.g.:\r
 \r
-    c:\> set WORKSPACE=C:\MyWork\edkii\r
+    c:\> set WORKSPACE=C:\MyWork\edk2\r
 \r
 You may need to edit the text files Tools/Conf/target.txt and\r
 Tools/Conf/tools_def.txt (created by edksetup) using your favorite \r
@@ -364,7 +358,7 @@ paths (as per the default installation of the tools), so a customized
 tool installation may require this manual process.\r
 \r
 Once this is completed, you are ready to test the build, by executing:\r
-    c:\MyWork\edkii\> build\r
+    c:\MyWork\edk2\> build\r
 \r
 This command builds the active platform specified in text file target.txt. If \r
 the active platform is not specified, go to the sub-directory that contains FPD \r
@@ -381,7 +375,7 @@ In the command window:
     c:\<directory>\> build\r
 or\r
   cd to the platform (FPD file) that you want to build and execute this command:\r
-    c:\MyWork\edkii\EdkNt32Pkg\> build\r
+    c:\MyWork\edk2\EdkNt32Pkg\> build\r
 \r
   Note that the active platform specified in target.txt overrides the platform \r
   specified by any FPD file in the current directory. For more   information \r
@@ -418,7 +412,7 @@ Individual Module Builds
 After running the setup command, you can build individual modules.\r
   In the command window, cd to the module that you want to build, and\r
   execute the build command:\r
-    c:\MyWork\edkii\MdePkg\Library\BaseLib\> build\r
+    c:\MyWork\edk2\MdePkg\Library\BaseLib\> build\r
 \r
   You must set the active platform in target.txt for individual module builds. \r
 \r