tyler.durden
/
audk
mirror of https://github.com/acidanthera/audk.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated BuildNotes.txt according to new packages name: 

Changed MdePkg to OldMdePkg in the text.

git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@2685 6f19259b-4bc3-4df7-8a09-765794883524
This commit is contained in:
vanjeff 2007-06-20 05:35:00 +00:00
parent fb3df220f8
commit 6e4c64c004
1 changed files with 104 additions and 104 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
BuildNotes.txt
View File

@ -6,7 +6,7 @@ Root Package 1.00
Intel is a trademark or registered trademark of Intel Corporation or its
subsidiaries in the United States and other countries.
* Other names and brands may be claimed as the property of others.
Copyright (c) 2006, Intel Corporation
Copyright (c) 2006 - 2007, Intel Corporation
This document provides updates to documentation, along with a description on
how to install and build the EDK II.
@ -14,7 +14,7 @@ how to install and build the EDK II.
Package Contents
----------------
BuildNotes.txt - The build notes for this package.
MdePkg - Industry-standard headers and libraries
OldMdePkg - Industry-standard headers and libraries
Tools - Build -specific tools that are designed to help the
developer create and modify drivers and libraries
EdkModulePkg - Reference drivers
@ -24,7 +24,7 @@ Package Contents
EdkUnixPkg - Posix/Unix Emulation platform reference (Currently this
builds only on ia32 Linux, but is meant to be portable.)
Note: MDE and MDK that appear in other documentation refer to the MdePkg and
Note: MDE and MDK that appear in other documentation refer to the OldMdePkg and
Tools packages, respectively. While, these two packages are the minimum
requirement for developing EDK II Packages we recommend that you download all
of the top-level files listed above.
@ -218,7 +218,7 @@ Cygwin, Linux, and 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, EdkModulePkg and EdkUnixPkg are currently supported by gcc
Only the OldMdePkg, EdkModulePkg and EdkUnixPkg 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.
@ -282,7 +282,7 @@ 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.
you would like to build (OldMdePkg/ or EdkModulePkg/) and then type build.
----------------------------
A Word on compiling on Linux
@ -516,7 +516,7 @@ Individual Module Builds
After running the setup command, you can build individual modules.
In the command window, cd to the module that you want to build, and
execute the build command:
c:\MyWork\edk2\MdePkg\Library\BaseLib\> build
c:\MyWork\edk2\OldMdePkg\Library\BaseLib\> build
You must set the active platform in target.txt for individual module builds.