From af9a0f8f67aafaf5c7ffca7bcb664680502a1880 Mon Sep 17 00:00:00 2001 From: bbahnsen Date: Thu, 27 Jul 2006 15:55:59 +0000 Subject: More info on gcc build. git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@1123 6f19259b-4bc3-4df7-8a09-765794883524 --- ReleaseNotes.txt | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) (limited to 'ReleaseNotes.txt') diff --git a/ReleaseNotes.txt b/ReleaseNotes.txt index d10f1ef..de39245 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 -- cgit v1.1