X-Git-Url: https://git.proxmox.com/?p=mirror_edk2.git;a=blobdiff_plain;f=ReleaseNotes.txt;h=d3b5a719a9632443343acef3226dbb48b6de6e40;hp=f9805025012c6939024132135e57b8ab62393f0b;hb=241876c7a32330e31ce3e11b01d0246b28e81cfb;hpb=70edbc34be395ef9697422c88cb436e1c8e3404b diff --git a/ReleaseNotes.txt b/ReleaseNotes.txt index f980502501..d3b5a719a9 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 @@ -217,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.) @@ -262,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. @@ -277,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. @@ -325,10 +385,10 @@ To exit the Nt32 emulation platform, type 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 should be restricted - to a single word, containing alphanumeric characters, with special characters, - underscore, dash and the period character also allowed. Space characters and - other special characters are not allowed. + 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