From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: intel.com, ip: 192.55.52.88, mailfrom: liming.gao@intel.com) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by groups.io with SMTP; Sun, 23 Jun 2019 20:15:39 -0700 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Jun 2019 20:15:38 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.63,410,1557212400"; d="scan'208";a="169333881" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by FMSMGA003.fm.intel.com with ESMTP; 23 Jun 2019 20:15:37 -0700 Received: from fmsmsx155.amr.corp.intel.com (10.18.116.71) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.439.0; Sun, 23 Jun 2019 20:15:37 -0700 Received: from shsmsx106.ccr.corp.intel.com (10.239.4.159) by FMSMSX155.amr.corp.intel.com (10.18.116.71) with Microsoft SMTP Server (TLS) id 14.3.439.0; Sun, 23 Jun 2019 20:15:36 -0700 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.185]) by SHSMSX106.ccr.corp.intel.com ([169.254.10.89]) with mapi id 14.03.0439.000; Mon, 24 Jun 2019 11:15:34 +0800 From: "Liming Gao" To: "Fan, ZhijuX" , "devel@edk2.groups.io" CC: "Feng, Bob C" Subject: Re: [PATCH] BaseTools:Remove unused Edk2\BuildNotes2.txt Thread-Topic: [PATCH] BaseTools:Remove unused Edk2\BuildNotes2.txt Thread-Index: AdUlorUE0pCTwwSBQ56WK8HcKx4YBAEmFwpQ Date: Mon, 24 Jun 2019 03:15:34 +0000 Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E48B2C0@SHSMSX104.ccr.corp.intel.com> References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNzhlZTc2NmEtNmM5MS00MTQ1LWI4ZTctMDg3NzBjNjEyZWY1IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiZ3lVMUN3bTZYdGtcLzE2TlloNzh2Zzkrem9vZW0ybm1xd1RxZEl5Smh1ZEFaTGYwT1NKc2FaY1N3NUVwQ2dDZFkifQ== dlp-product: dlpe-windows dlp-version: 11.0.600.7 dlp-reaction: no-action x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Return-Path: liming.gao@intel.com Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Reviewed-by: Liming Gao > -----Original Message----- > From: Fan, ZhijuX > Sent: Tuesday, June 18, 2019 2:55 PM > To: devel@edk2.groups.io > Cc: Gao, Liming ; Feng, Bob C > Subject: [PATCH] BaseTools:Remove unused Edk2\BuildNotes2.txt >=20 > BZ:https://bugzilla.tianocore.org/show_bug.cgi?id=3D1889 >=20 > Edk2\BuildNotes2.txt is not maintained any more. User can find the > related info in wiki. So, this file can be removed. >=20 > Cc: Bob Feng > Cc: Liming Gao > Signed-off-by: Zhiju.Fan > --- > BuildNotes2.txt | 154 --------------------------------------------------= ------ > 1 file changed, 154 deletions(-) > delete mode 100644 BuildNotes2.txt >=20 > diff --git a/BuildNotes2.txt b/BuildNotes2.txt > deleted file mode 100644 > index 8bf4f6930a..0000000000 > --- a/BuildNotes2.txt > +++ /dev/null > @@ -1,154 +0,0 @@ > -Intel(R) Platform Innovation Framework for EFI > -EFI Development Kit II (EDK II) > -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 - 2011, Intel Corporation. All rights reserved. > - > -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) > - > - > -------------------------------------------------------------------------= ------- > -The most recent version of the setup instructions is available on the ED= K II > -web-site: > - https://github.com/tianocore/tianocore.github.io/wiki/Getting%20Starte= d%20with%20EDK%20II > - > - > -------------------------------------------------------------------------= ------- > -Quick Start (Windows Development Platform) > ------------ > - > -In a command prompt window, change to the top-level directory of the EDK= II > -source. > - > -Note: > - The first time the edksetup script is executed, it creates three files= in the > - %WORKSPACE%\Conf directory. The files: tools_def.txt, target.txt and > - build_rule.txt, are only created if they do not exist, if they exist, = they > - are not touched. > - > -First, set up your project workspace. If you have previously initialized= this > -WORKSPACE, and a newer version of the *.template files in > -WORKSPACE\BaseTools\Conf exists, remove the *.txt files in the WORKSPACE= \Conf > -directory prior to running the edksetup script. > - > -For the reference build of the Nt32 Platform emulation environment, use = the > -edksetup.bat option: --nt32. For building other platforms or modules, th= is > -option is not required, as Visual Studio standard includes, libraries an= d/or > -dlls are not required for normal development. > - > - c:\MyWork\edk2\> edksetup --nt32 > - > -The default tool chain (named MYTOOLS) is pre-configured to use VS2008 f= or IA32 > -and X64 target architectures and DDK3790 for IPF target architectures. T= o use a > -different tool chain, either modify the tools_def.txt file's MYTOOLS ent= ries, > -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 di= fferent > -tool chain tag name: build -t VS2008 ... , for example. Using this meth= od 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 VS2008x= 86. > - > - > -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. > - > -Change the following line > - ACTIVE_PLATFORM =3D MdeModulePkg/MdeModulePkg.dsc > -to > - ACTIVE_PLATFORM =3D MdePkg/MdePkg.dsc > - > -Then go to MdePkg\Library\BaseLib directory and type build: > - c:\MyWork\edk2\> cd MdePkg\Library\BaseLib > - c:\MyWork\edk2\> build > - > -If you want build a platform, ACTIVE_PLATFORM must be set to your desire= d > -platform dsc file, go to directory which must be not a module's director= y, and > -run "build" command. > - > -Instead of changing Target.txt, you can specify platform, module and/or > -architecture on command line. > -For example, if you want to build NT32 platform, you can just type > - > - c:\MyWork\edk2\> build -p Nt32Pkg\Nt32Pkg.dsc -a IA32 > - > -and if you want to build HelloWorld module, you can just type > - > - c:\MyWork\edk2\> build -p Nt32Pkg\Nt32Pkg.dsc -a IA32 -m MdeModulePk= g\Application\HelloWorld\HelloWorld.inf > - > -Other helpful command line options of build tool include "-v" and "-d". > -The "-v" option is used to turn on the verbose build, which provide more > -information during the build. "-d " option is used to > -turn on the debug information which is helpful debugging build tools. > - > -For more information on build options, please try "build -h" on command = line. > - > -Note: > - The Windows style help option "/?" is not a valid option for the build > - command. > - > - > -------------------------------------------------------------------------= ------- > -Supported build targets > ------------------------ > - > -all - Build whole platform or module. It can be ignored. > -genc - Generate AutoGen.c, AutoGen.h and .depex files o= nly. > -genmake - Generate makefiles in addition to files generated by "genc" = target. > -clean - Clean intermediate files > -cleanall - Clean all generated files and directories during build, exce= pt the > - generated Makefile files (top level and module makefiles) > -cleanlib - Clean all generated files and directories during library bui= ld > -run - Launch NT32 shell (only valid for NT32 platform) > - > -------------------------------------------------------------------------= ------- > -Tools in Python > ---------------- > - > -* Run build tool written in Python from source > - It can be executed from its source directly as long as you have the Py= thon > - interpreter (version 2.5.4) installed. The source code is located at > - WORKSPACE/BaseTools. > - > - where: > - > - build/build.py - The entry tool of build tools > - > - "build.py" steps: > - 1. Run "edksetup.bat" > - 2. set PYTHONPATH to the local directory of above source > - (BaseTools/Source/Python) > - 3. Set ACTIVE_PLATFORM in WORKSPACE\Conf > - 4. Go to platform or module directory > - 5. Run " /build/build.py"= or > - "/build/build.py" directly. > - > -* Convert Python source to exe file > - The tools written in Python can be converted into executable program w= hich can > - be executed without Python interpreter. One of the conversion tools is= called > - cx_Freeze, available at: > - > - http://sourceforge.net/projects/cx-freeze/ > - > - If you have installed cx_Freeze at c:\cx_Freeze-3.0.3. Use the followi= ng > - command lines to convert MyBuild.py to a Windows executable. > - > - set PYTHONPATH=3D\BaseTools\Source\Python > - c:\cx_Freeze-3.0.3\FreezePython.exe --include-modules=3Dencodings.cp= 437,encodings.gbk,encodings.utf_16,encodings.utf_8 > --install-dir=3D.\mybuild MyBuild.py > - > - The generated .exe files are put in "mybuild" subdirectory. > - > -- > 2.14.1.windows.1