From: lhauch Date: Mon, 28 Apr 2008 18:21:58 +0000 (+0000) Subject: Added paragraph on tool chain usage X-Git-Url: http://git.etherboot.org/people/mcb30/edk2.git/commitdiff_plain/417c199bd904a5a3d9707954900bd3b4f2f37b08?ds=sidebyside Added paragraph on tool chain usage git-svn-id: https://edk2.tianocore.org/svn/edk2/trunk@5144 de2fecce-e211-0410-80a6-f3fac2684e05 --- diff --git a/www/installation.html b/www/installation.html index b3d26d951..2a66d1481 100644 --- a/www/installation.html +++ b/www/installation.html @@ -277,6 +277,10 @@ has been pre-populated with the standard location for the Microsoft tool chains and includes the standard location of the Intel C Compiler for EFI Byte Code (EBC).

+

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 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.

Once the external tools are installed and the environment variables are set, you can try a build.

@@ -287,7 +291,7 @@ Win32 binaries of the EDK II tools used in edk2 development. It will fail if the external tools above are not properly installed.
Using the --nt32 switch will run "%VS80COMNTOOLS%\vsvars32" (VS2005) or - "%VS71COMNTOOLS%\vsvars32" (VS2003.NET) to setup standard C FLAGS, + "%VS71COMNTOOLS%\vsvars32" (VS2003 .NET) to setup standard C FLAGS, Library and Include locations to build the Nt32 emulation environment.
Note: If you do not want to build the Nt32 emulation environment, you do not need to use the --nt32 switch or run vsvars32.bat.