BaseTools: Library hashing fix and optimization for --hash feature

[mirror_edk2.git] / BuildNotes2.txt

diff --git a/BuildNotes2.txt b/BuildNotes2.txt
index 5798938469617c72d4e0f46163877a1610a83843..8bf4f6930a7769d91e5b1bbfee40e9ba94de255c 100644 (file)
--- a/BuildNotes2.txt
+++ b/BuildNotes2.txt
@@ -1,14 +1,14 @@
 Intel(R) Platform Innovation Framework for EFI\r
 EFI Development Kit II (EDK II)\r
-2010-03-31\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 - 2010, Intel Corporation. All rights reserved.\r
+Copyright (c) 2007 - 2011, Intel Corporation. All rights reserved.\r
 \r
-EDK II packages can be checked out from the following SVN address:\r
-http://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2 \r
+EDK II packages can be gathered from the following address:\r
+  https://github.com/tianocore/edk2.git\r
 \r
 The detailed introduction of these packages can be found in each package\r
 description file. (The *.dec file under the package directory)\r
@@ -17,7 +17,7 @@ description file. (The *.dec file under the package directory)
 -------------------------------------------------------------------------------\r
 The most recent version of the setup instructions is available on the EDK II\r
 web-site:\r
-  http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Step-by-step_instructions\r
+  https://github.com/tianocore/tianocore.github.io/wiki/Getting%20Started%20with%20EDK%20II\r
 \r
 \r
 -------------------------------------------------------------------------------\r
@@ -45,26 +45,27 @@ dlls are not required for normal development.
 \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
@@ -118,12 +119,10 @@ run       - Launch NT32 shell (only valid for NT32 platform)
 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
-    http://edk2-buildtools.svn.sourceforge.net/svnroot/edk2-buildtools/trunk/BaseTools\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
@@ -139,7 +138,7 @@ Tools in Python
        "<python_source_dir>/build/build.py" directly.\r
 \r
 * Convert Python source to exe file\r
-  The tools written in Python can be coverted into executable program which can\r
+  The tools written in Python can be converted into executable program which can\r
   be executed without Python interpreter. One of the conversion tools is called\r
   cx_Freeze, available at: \r
 \r