Intel(R) Platform Innovation Framework for EFI\r
-EFI Development Kit II Prime (EDK II Prime)\r
-Root Package 1.00\r
-2008-05-15\r
+EFI Development Kit II (EDK II)\r
+2011-12-14\r
\r
Intel is a trademark or registered trademark of Intel Corporation or its\r
subsidiaries in the United States and other countries.\r
* Other names and brands may be claimed as the property of others.\r
-Copyright (c) 2007 - 2008, Intel Corporation All rights reserved.\r
+Copyright (c) 2007 - 2011, Intel Corporation. All rights reserved.\r
\r
-EDK II Prime packages are in the development phase. They consist of:\r
+EDK II packages can be gathered from the following address:\r
+ https://github.com/tianocore/edk2.git\r
\r
- BuildNotes2.txt - The build notes for this package\r
- MdePkg - Industry-standard headers and libraries\r
- BaseTools - Build -specific tools that are designed to help the\r
- developer create and modify drivers and libraries\r
- IntelFrameworkPkg - Tiano/Framework Includes and Libraries\r
- MdeModulePkg - UEFI 2.1/PI 1.0 compliant modules\r
- IntelFrameworkModulePKg - Tiano/Framework Includes and Libraries\r
- Nt32Pkg - UEFI 2.1/PI 1.0 emulation environment for Windows\r
- FatBinPkg - Binaries built from the FatPkg \r
- EdkShellBinPkg - Binaries of full shell, minimum shell and commands\r
-\r
-Note:\r
- EdkShellBinPkg is supported to support both EDK II build and EDKII Prime\r
- build by having several module description files.\r
+The detailed introduction of these packages can be found in each package\r
+description file. (The *.dec file under the package directory)\r
\r
\r
-------------------------------------------------------------------------------\r
The most recent version of the setup instructions is available on the EDK II\r
web-site:\r
- https://edk2.tianocore.org/installation.html\r
+ https://github.com/tianocore/tianocore.github.io/wiki/Getting%20Started%20with%20EDK%20II\r
\r
\r
-------------------------------------------------------------------------------\r
\r
c:\MyWork\edk2\> edksetup --nt32\r
\r
-The default tool chain (named MYTOOLS) is pre-configured to use VS2005 for IA32\r
-and X64 target architectures and the DDK for IPF target architectures. To use a\r
+The default tool chain (named MYTOOLS) is pre-configured to use VS2008 for IA32\r
+and X64 target architectures and DDK3790 for IPF target architectures. To use a\r
different tool chain, either modify the tools_def.txt file's MYTOOLS entries,\r
or modify the %WORKSPACE%\Conf\target.txt file's TOOL_CHAIN_TAG. The pre-defined\r
tags are listed near the top of the %WORKSPACE%\Conf\tools_def.txt file, below\r
the Supported Tool Chains comment.\r
Alternatively, you may use the build command's -t option to specify a different\r
-tool chain tag name: build -t VS2003 ... , for example. Using this method will\r
-require that you always use the build command's -t option.\r
+tool chain tag name: build -t VS2008 ... , for example. Using this method will\r
+require that you always use the build command's -t option. If you use 64-bit \r
+Windows OS, you should use tool chain tag name with x86, such as VS2008x86.\r
\r
\r
-Next, go to the module directory and begin to build. This example is for the\r
+Next, go to the module directory and begin to build. This example is for the\r
HelloWorld application.\r
\r
c:\MyWork\edk2\> cd MdeModulePkg\Application\HelloWorld\r
c:\MyWork\edk2\> build\r
\r
If you want to build the a module in another package (for example, \r
-MdePkg\Library\BaseLib\BaseLib.inf), please edit the file,\r
-%WORKSPACE%\Conf\Target.txt, first.\r
+MdePkg\Library\BaseLib\BaseLib.inf), please edit the file\r
+%WORKSPACE%\Conf\Target.txt first.\r
\r
Change the following line\r
ACTIVE_PLATFORM = MdeModulePkg/MdeModulePkg.dsc\r
Tools in Python\r
---------------\r
\r
-* Run buld tool written in Python from source\r
- The build tool written in Python can be executed from its source directly as\r
- long as you have the Python interpreter (version 2.5) installed. The source\r
- of Python code is locating at:\r
-\r
- https://buildtools.tianocore.org/svn/buildtools/trunk/BaseTools/Source/Python\r
+* Run build tool written in Python from source\r
+ It can be executed from its source directly as long as you have the Python\r
+ interpreter (version 2.5.4) installed. The source code is located at\r
+ WORKSPACE/BaseTools.\r
\r
where:\r
\r
build/build.py - The entry tool of build tools\r
- AutoGen/AutoGen.py - Generate AutoGen.c/.h and makefile only\r
\r
"build.py" steps:\r
1. Run "edksetup.bat"\r
5. Run "<python_interpreter.exe> <python_source_dir>/build/build.py" or\r
"<python_source_dir>/build/build.py" directly.\r
\r
- "AutoGen.py" steps:\r
- 1. Run "edksetup.bat"\r
- 2. set PYTHONPATH to the local directory of above source\r
- (BaseTools/Source/Python)\r
- 3. Set ACTIVE_PLATFORM in WORKSPACE\Conf\r
- 4. Run "<python_interpreter.exe> <python_source_dir>/AutoGen/AutoGen.py" or\r
- "<python_source_dir>/AutoGen/AutoGen.py"\r
-\r
* Convert Python source to exe file\r
The tools written in Python can be coverted into executable program which can\r
be executed without Python interpreter. One of the conversion tools is called\r
projects / mirror_edk2.git / blobdiff