-Microsoft Windows 32-bit Operating Systems are located in the Bin\Win32 directory.\r
-\r
-The binary tools will be updated only after passing developer testing.\r
-\r
-The BaseTools package will be updated with new tools only after all testing on a set\r
-of binary tools has successfully completed.\r
-\r
-Current state of the tools is Proto-Type - not all tool functions have been implemented\r
-and there may be bugs in these tools. These tools are under constant development at\r
-this time.\r
-\r
-BaseTools Simple Usage:\r
-1) Change the directory to the EDK2 root directory, where the edksetup.bat is\r
-2) Run "edksetup.bat NewBuild"\r
-3) Set the ACTIVE_PLATFORM to your desired platform description file \r
- (%WORKSPACE%\Conf\target.txt)\r
-4) To build platform, run "build" command in non-module directory\r
-5) To build module individually, run "build" command in module directory, i.e. where the \r
- *.inf file is\r
-\r
-Notes:\r
-1) Only *.efi files can be generated. Flash image cannot be generated at present.\r
-2) Only "clean" and "cleanall" build target are supported, in both top level \r
- makefile and module's makefile. \r
-3) Not all tool chains and target architectures are tested. Due to both tools \r
- and source code limitations, ther must be bugs in it. Please report any issue \r
- ASAP so we can fix it soon.\r
-4) The tree structure generated by build tools is similar to Ant build system.\r
-5) Makefile can be called directly by nmake for both top level platform and module. But\r
- after you call "nmake cleanall", you have to call "build" command to rebuild platform\r
- or modules because the AutoGen.* files have been be removed. The "makefile" itself\r
- cannot generate AutoGen.* files. Only "build" command can.\r
-\r
-25-Jun-2007\r
+Microsoft Windows 32-bit Operating Systems are located in the Bin\Win32 directory, other \r
+directory contatins tools source.\r
+\r
+1. Build step to generate the binary tools.\r
+\r
+=== Windows/Visual Studio Notes ===\r
+\r
+To build the BaseTools, you should run the standard vsvars32.bat script\r
+from your preferred Visual Studio installation or you can run get_vsvars.bat\r
+to use latest automatically detected version.\r
+\r
+In addition to this, you should set the following environment variables:\r
+\r
+ * EDK_TOOLS_PATH - Path to the BaseTools sub directory under the edk2 tree\r
+ * BASE_TOOLS_PATH - The directory where the BaseTools source is located.\r
+ (It is the same directory where this README.txt is located.)\r
+ * PYTHON_FREEZER_PATH - Path to where the python freezer tool is installed\r
+\r
+After this, you can run the toolsetup.bat file, which is in the same\r
+directory as this file. It should setup the remainder of the environment,\r
+and build the tools if necessary.\r
+\r
+Please also refer to the 'BuildNotes.txt' file for more information on\r
+building under Windows.\r
+\r
+=== Unix-like operating systems ===\r
+\r
+To build on Unix-like operating systems, you only need to type 'make' in\r
+the base directory of the project.\r
+\r
+=== Ubuntu Notes ===\r
+\r
+On Ubuntu, the following command should install all the necessary build\r
+packages to build all the C BaseTools:\r
+\r
+ sudo apt-get install build-essential uuid-dev\r
+\r
+=== Python sqlite3 module ===\r
+On Windows, the cx_freeze will not copy the sqlite3.dll to the frozen \r
+binary directory (the same directory as build.exe and GenFds.exe). \r
+Please copy it manually from <PythonHome>\DLLs.\r
+\r
+The Python distributed with most recent Linux will have sqlite3 module\r
+built in. If not, please install sqlit3 package separately.\r
+\r
+26-OCT-2011\r
projects / mirror_edk2.git / blobdiff