Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Tree [848d67] svn/branches/Dev /
History



File Date Author Commit
Bin 2010-04-29 hhtian hhtian [8a3500] Update the copyright notice format
BinWrappers 2010-10-15 andrewfish andrewfish [708cb2] Fix build issue on 64-bit Snow Leopard kernel. ...
Conf 2010-12-23 vanjeff vanjeff [cd03c8] Roll back SUBSYSTEM type to CONSOLE for ASLDLIN...
Scripts 2010-04-29 geekboy15a geekboy15a [19dc28] Added support to build with GCC 4.4 in X64 mode.
Source 2011-01-24 lhauch lhauch [848d67] BaseToolsDev[-<AutoGen>]: Merged changes from t...
Tests 2010-04-29 hhtian hhtian [8a3500] Update the copyright notice format
UserManuals 2010-12-08 jsu1 jsu1 [269040] Rm_Pkg_Utility_man_page update
gcc 2010-06-29 geekboy15a geekboy15a [0ba9fc] Removed the download of the MinGW headers as th...
BuildEnv 2010-07-09 geekboy15a geekboy15a [7526bb] Fixed issue where default tools could not be fo...
BuildNotes.txt 2010-04-29 hhtian hhtian [8a3500] Update the copyright notice format
GNUmakefile 2010-04-29 hhtian hhtian [8a3500] Update the copyright notice format
Makefile 2010-04-29 hhtian hhtian [8a3500] Update the copyright notice format
ReadMe.txt 2009-07-17 lgao4 lgao4 [5e575d] Remove binary tools.
building-gcc.txt 2009-07-17 lgao4 lgao4 [edcd03] Check in the tools executables for
toolsetup.bat 2010-04-29 hhtian hhtian [8a3500] Update the copyright notice format

Read Me

This directory contains the next generation of EDK II build tools and template files.
Templates are located in the Conf directory, other directory contatins tools source.

Build step to generate the binary tools.

=== Windows/Visual Studio Notes ===

To build the BaseTools, you should run the standard vsvars32.bat script.

In addition to this, you should set the following environment variables:

 * EDK_TOOLS_PATH - Path to the BaseTools sub directory under the edk2 tree
 * BASE_TOOLS_PATH - The directory where the BaseTools source is located.
   (It is the same directory where this README.txt is located.)
 * PYTHON_FREEZER_PATH - Path to where the python freezer tool is installed

After this, you can run the toolsetup.bat file, which is in the same
directory as this file.  It should setup the remainder of the environment,
and build the tools if necessary.

Please also refer to the 'BuildNotes.txt' file for more information on
building under Windows.

=== Unix-like operating systems ===

To build on Unix-like operating systems, you only need to type 'make' in
the base directory of the project.

=== Ubuntu Notes ===

On Ubuntu, the following command should install all the necessary build
packages to build all the C BaseTools:

  sudo apt-get install build-essentials uuid-dev

=== Python sqlite3 module ===
On Windows, the cx_freeze will not copy the sqlite3.dll to the frozen 
binary directory (the same directory as build.exe and GenFds.exe). 
Please copy it manually from <PythonHome>\DLLs.

The Python distributed with most recent Linux will have sqlite3 module
built in. If not, please install sqlit3 package separately.

17-July-2009