More info on gcc build.

[mirror_edk2.git] / ReleaseNotes.txt

diff --git a/ReleaseNotes.txt b/ReleaseNotes.txt
index d10f1efd0193c5dbe39afcb32d22a7e595c799c6..de392458bb5187e4ff494ab88ebf95a9a90e3104 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
 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
 \r
 ----------------------------\r
 A Word on compiling on Linux\r