X-Git-Url: https://git.proxmox.com/?p=mirror_edk2.git;a=blobdiff_plain;f=ReleaseNotes.txt;h=de392458bb5187e4ff494ab88ebf95a9a90e3104;hp=34254e61c7513f478f7bbc0ca1d7ee71d756a918;hb=af9a0f8f67aafaf5c7ffca7bcb664680502a1880;hpb=561e4a76570036d92841f0a613ef382304a2ee87

diff --git a/ReleaseNotes.txt b/ReleaseNotes.txt
index 34254e61c7..de392458bb 100644
--- a/ReleaseNotes.txt
+++ b/ReleaseNotes.txt
@@ -1,7 +1,7 @@
 Intel(R) Platform Innovation Framework for EFI
 EFI Development Kit II (EDK II) 
 Root Package 1.00
-2006-07-13
+2006-07-18
 
 Intel is a trademark or registered trademark of Intel Corporation or its 
 subsidiaries in the United States and other countries.
@@ -192,6 +192,59 @@ many other POSIX-compliant host operating environments. To compile the custom
 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. 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
+----------------------------
+
+In order to compile on Linux, you will need to have the e2fsprogs-dev package
+installed.  Check your distribution for the rpm, deb or other package format.
+This package contains the uuid library and header that are used by some of the
+host tools.
+
+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
@@ -318,12 +371,18 @@ or
   about active platform policy, see the “EDK II Build and Packaging Architecture
   Specification.” 
 
-To run the Nt32 emulation platform under Microsoft Windows, go to <full build path>\DEBUG\MSFT\IA32 and execute SecMain.exe
+To run the Nt32 emulation platform under Microsoft Windows, go to 
+<full build path>\DEBUG\MSFT\IA32 and execute SecMain.exe
 
 To exit the Nt32 emulation platform, type “reset” at the EFI Shell>
 command prompt.  Alternatively, from the graphical interface, select the Boot
 Maintenance Manager's “Reset System” command.
 
+      NOTE: When creating a new platform, the Platform Name is restricted
+      to a single word containing alphanumeric characters, underscore, dash, 
+      and period.  The space character and other special characters are 
+      not allowed.
+
 -----------------------
 Notes on Symbolic Debug
 -----------------------