X-Git-Url: https://git.proxmox.com/?p=mirror_edk2.git;a=blobdiff_plain;f=ReleaseNotes.txt;h=d3b5a719a9632443343acef3226dbb48b6de6e40;hp=0efa80764ade564aa957e69168762c5edddd8e76;hb=241876c7a32330e31ce3e11b01d0246b28e81cfb;hpb=6329bec1033d1685a62f7cbe06a34737758830a0

diff --git a/ReleaseNotes.txt b/ReleaseNotes.txt
index 0efa80764a..d3b5a719a9 100644
--- 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).
 
 Only the MdePkg and EdkModulePkg are currently supported by gcc builds. Other
-builds, such as the EdkNt32Pkg, will not compile with gcc.
+builds, such as the EdkNt32Pkg, will not compile with gcc. By default, the edk2
+will try to build the NT32.fpd, which is not supported by gcc. So, you need to
+change the Tools/Conf/target.txt.
+
+The platform to be built is identified by the Tools/Conf/target.txt file:
+
+#
+#  PROPERTY              Type       Use         Description
+#  ----------------      --------   --------    -----------------------------------------------------------
+#  ACTIVE_PLATFORM       Filename   Recommended Specify the WORKSPACE relative Path and Filename 
+#                                               of the platform FPD file that will be used for the build
+#                                               This line is required if and only if the current working
+#                                               directory does not contain one or more FPD files.
+
+ACTIVE_PLATFORM       =
+ 
+You can leave it black, as above, or set it to any .fpd file in the workspace.
+If you leave it blank, then you just cd to the dir that contains the .fpd that
+you would like to build (MdePkg/ or EdkModulePkg/) and then type build.
 
 ----------------------------
 A Word on compiling on Linux
@@ -208,6 +226,26 @@ If you are running on x86_64 Linux, then you should install a 64 bit version of
 the Java JDK. The version that was used was jdk-1_5_0_07-linux-amd64-rpm.bin.
 It may be downloaded from sun.com.
 
+-----------------------------------------
+A Word on compiling under Cygwin with gcc
+-----------------------------------------
+
+Cygwin is a POSIX style operating environment for Windows. It is possible to
+compile the EDK 2 using gcc and cygwin. There are a few extra steps necessary
+to make this happen. There is a JNI (Java Native Interface) library in the
+Tools.  In order to compile this under Cygwin, the 'linux' java headers must be
+installed to the $JAVA_HOME dir on the windows system. To accomplish this, you
+must install the JDK on a linux system, and then copy
+linux:$JAVA_HOME/include/linux/ to windows:$JAVA_HOME/include. These are really
+typedefs needed by gcc.
+
+Compiling under cygwin is slow, because the underlying file accesses are slow
+in cygwin. For this reason, we do not encourage the use of cygwin. A true unix
+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
+cygwin. It is necessary for the GenFvImage tool.
+
 -----------------------
 Notes on Documentation
 -----------------------
@@ -232,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.
 
 To test your tool chain setup and to build the supplied tools, execute:
-    c:\MyWork\edkii\> edksetup ForceBuild
+    c:\MyWork\edkii\> edksetup ForceRebuild
 
 (The edksetup script is referred to as the setup command throughout the 
 rest of this document.)
@@ -277,13 +315,20 @@ environment variable, TOOL_CHAIN to "gcc" before running the
 edksetup script.  Example: export TOOL_CHAIN=gcc
 
 To test your tool chain setup and to build the supplied tools, execute:
-    c:\MyWork\edkii\> edksetup ForceBuild
+    c:\MyWork\edkii\> edksetup ForceRebuild
 
 On Linux systems, you must source the edksetup.sh file to load the correct
 settings into your shell.
 
     . edksetup.sh # Note the dot.
 
+If you have recently updated your code from subversion, the tools will need to
+be rebuilt if there were any code changes made to them. You can request that
+the tools get rebuilt by typing:
+
+    . edksetup.sh Rebuild # Unix-like systems
+    edksetup.bat Rebuild  # Windows
+
 The edksetup script is referred to as the setup command throughout the 
 rest of this document.
       NOTE: You should run the setup command at the start of every session.
@@ -292,7 +337,7 @@ rest of this document.
 
 Any changes to the tool source code or XML Schema documents require that
 you execute the following:
-   c:\MyWork\edkii\> edksetup ForceBuild
+   c:\MyWork\edkii\> edksetup ForceRebuild
 
 You must set the WORKSPACE environment variable, or run the edksetup
 script (without any arguments), any time you want to build.