X-Git-Url: https://git.proxmox.com/?p=mirror_edk2.git;a=blobdiff_plain;f=BuildNotes2.txt;h=8bf4f6930a7769d91e5b1bbfee40e9ba94de255c;hp=3e6f6f96d068a25d47240ab947768bbf1846eef5;hb=5a9e23ceb991f3bd0eea74d6b67f9102f65ea6bc;hpb=caf304693aad8886de5f387a80890b1623489147

diff --git a/BuildNotes2.txt b/BuildNotes2.txt
index 3e6f6f96d0..8bf4f6930a 100644
--- a/BuildNotes2.txt
+++ b/BuildNotes2.txt
@@ -1,14 +1,14 @@
 Intel(R) Platform Innovation Framework for EFI
 EFI Development Kit II (EDK II)
-2010-03-31
+2011-12-14
 
 Intel is a trademark or registered trademark of Intel Corporation or its
 subsidiaries in the United States and other countries.
 * Other names and brands may be claimed as the property of others.
-Copyright (c) 2007 - 2010, Intel Corporation  All rights reserved.
+Copyright (c) 2007 - 2011, Intel Corporation. All rights reserved.
 
-EDK II packages can be checked out from the following SVN address:
-http://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2 
+EDK II packages can be gathered from the following address:
+  https://github.com/tianocore/edk2.git
 
 The detailed introduction of these packages can be found in each package
 description file. (The *.dec file under the package directory)
@@ -17,7 +17,7 @@ description file. (The *.dec file under the package directory)
 -------------------------------------------------------------------------------
 The most recent version of the setup instructions is available on the EDK II
 web-site:
-  http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Step-by-step_instructions
+  https://github.com/tianocore/tianocore.github.io/wiki/Getting%20Started%20with%20EDK%20II
 
 
 -------------------------------------------------------------------------------
@@ -45,26 +45,27 @@ dlls are not required for normal development.
 
     c:\MyWork\edk2\> edksetup --nt32
 
-The default tool chain (named MYTOOLS) is pre-configured to use VS2005 for IA32
-and X64 target architectures and the DDK for IPF target architectures. To use a
+The default tool chain (named MYTOOLS) is pre-configured to use VS2008 for IA32
+and X64 target architectures and DDK3790 for IPF target architectures. To use a
 different tool chain, either modify the tools_def.txt file's MYTOOLS entries,
 or modify the %WORKSPACE%\Conf\target.txt file's TOOL_CHAIN_TAG. The pre-defined
 tags are listed near the top of the %WORKSPACE%\Conf\tools_def.txt file, below
 the Supported Tool Chains comment.
 Alternatively, you may use the build command's -t option to specify a different
-tool chain tag name: build -t VS2003 ... , for example.  Using this method will
-require that you always use the build command's -t option.
+tool chain tag name: build -t VS2008 ... , for example.  Using this method will
+require that you always use the build command's -t option. If you use 64-bit 
+Windows OS, you should use tool chain tag name with x86, such as VS2008x86.
 
 
-Next, go to the module directory and begin to build.  This example is for the
+Next, go to the module directory and begin to build. This example is for the
 HelloWorld application.
 
     c:\MyWork\edk2\> cd MdeModulePkg\Application\HelloWorld
     c:\MyWork\edk2\> build
 
 If you want to build the a module in another package (for example, 
-MdePkg\Library\BaseLib\BaseLib.inf), please edit the file,
-%WORKSPACE%\Conf\Target.txt, first.
+MdePkg\Library\BaseLib\BaseLib.inf), please edit the file
+%WORKSPACE%\Conf\Target.txt first.
 
 Change the following line
     ACTIVE_PLATFORM       = MdeModulePkg/MdeModulePkg.dsc
@@ -118,12 +119,10 @@ run       - Launch NT32 shell (only valid for NT32 platform)
 Tools in Python
 ---------------
 
-* Run buld tool written in Python from source
-  The build tool written in Python can be executed from its source directly as
-  long as you have the Python interpreter (version 2.5) installed. The source
-  of Python code is locating at:
-
-    http://edk2-buildtools.svn.sourceforge.net/svnroot/edk2-buildtools/trunk/BaseTools
+* Run build tool written in Python from source
+  It can be executed from its source directly as long as you have the Python
+  interpreter (version 2.5.4) installed. The source code is located at
+  WORKSPACE/BaseTools.
 
   where:
 
@@ -139,7 +138,7 @@ Tools in Python
        "<python_source_dir>/build/build.py" directly.
 
 * Convert Python source to exe file
-  The tools written in Python can be coverted into executable program which can
+  The tools written in Python can be converted into executable program which can
   be executed without Python interpreter. One of the conversion tools is called
   cx_Freeze, available at: