From cc19f426d28499373b31fc762d4a6cebb96e3558 Mon Sep 17 00:00:00 2001 From: Guo Mang Date: Mon, 26 Dec 2016 17:28:04 +0800 Subject: Remove unused files Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Guo Mang --- BuildNotes2.txt | 154 ----------------- Edk2Setup.bat | 508 -------------------------------------------------------- Maintainers.txt | 221 ------------------------ 3 files changed, 883 deletions(-) delete mode 100644 BuildNotes2.txt delete mode 100755 Edk2Setup.bat delete mode 100644 Maintainers.txt diff --git a/BuildNotes2.txt b/BuildNotes2.txt deleted file mode 100644 index 45520536a2..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 EDK II -web-site: - https://github.com/tianocore/tianocore.github.io/wiki/Getting%20Started%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, this -option is not required, as Visual Studio standard includes, libraries and/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 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 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 -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 = MdeModulePkg/MdeModulePkg.dsc -to - ACTIVE_PLATFORM = 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 desired -platform dsc file, go to directory which must be not a module's directory, 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 MdeModulePkg\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 only. -genmake - Generate makefiles in addition to files generated by "genc" target. -clean - Clean intermediate files -cleanall - Clean all generated files and directories during build, except the - generated Makefile files (top level and module makefiles) -cleanlib - Clean all generated files and directories during library build -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 Python - 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 coverted into executable program which 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 following - command lines to convert MyBuild.py to a Windows executable. - - set PYTHONPATH=\BaseTools\Source\Python - c:\cx_Freeze-3.0.3\FreezePython.exe --include-modules=encodings.cp437,encodings.gbk,encodings.utf_16,encodings.utf_8 --install-dir=.\mybuild MyBuild.py - - The generated .exe files are put in "mybuild" subdirectory. - diff --git a/Edk2Setup.bat b/Edk2Setup.bat deleted file mode 100755 index 2d132349bc..0000000000 --- a/Edk2Setup.bat +++ /dev/null @@ -1,508 +0,0 @@ -@REM @file -@REM Windows batch file, Edk2Setup.bat, to set up an EDK II build environment -@REM -@REM This script will be renamed to edksetup.bat after initial testing and -@REM acceptance by the open source community. -@REM -@REM This script will set the following system environment variables: -@REM WORKSPACE, EDK_TOOLS_PATH, PATH -@REM If rebuilding the tools: -@REM BASE_TOOLS_PATH, PYTHON_FREEZER_PATH, PYTHONPATH -@REM It will also create a Conf/target.txt, tools_def.txt and build_rule.txt files -@REM if they do not exist -@REM If the reset flag is set, all environment variables will be reset and -@REM the Conf/target.txt, tools_def.txt and build_rule.txt files will be overwritten -@REM -@REM Three other scripts, located in the BaseTools\Scripts directory, may be called -@REM by this script. -@REM SetVisualStudio.bat - will set the Visual Studio environment based on the --vs* flags -@REM it is also used to build the Win32 binaries, calling nmake -@REM using the WORKSPACE\BaseTools\Makefile -@REM ShowEnvironment.bat - will display the current EDK II Build environment -@REM UpdateBuildVersions.py - script is called prior to building the EDK II BaseTools from -@REM Sources. This tool will modify the BuildVersion.* files so that -@REM when the tools get built, they will have a custom version entry -@REM similar to the following: -@REM e:\edk2>build --version -@REM build.exe Version 0.51 Developer Build based on Revision: 15668 -@REM -@REM Copyright (c) 2014, Intel Corporation. All rights reserved.
-@REM This program and the accompanying materials -@REM are licensed and made available under the terms and conditions of the BSD License -@REM which accompanies this distribution. The full text of the license may be found at -@REM http://opensource.org/licenses/bsd-license.php -@REM -@REM THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS, -@REM WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED. -@REM -@REM -@REM usage: -@REM Edk2Setup.bat [--help | -h] [-v | --version] [-r | --reset] -@REM [--reconfig] [--edk-tools-path DirName] -@REM [--pull [Directory]| --rebuild [Directory]] -@REM [--nt32 [X64]] - -@REM ############################################################## -@REM # You should not have to modify anything below this line -@REM # -@echo off -@set SCRIPT_NAME=%0 -@set SCRIPT_VERSION=0.9.2. -@set SVN_REVISION=$Revision$ -@set RESET_ENVIRONMENT=FALSE -@set NT32PKG=FALSE -@set NT32_X64= -@set BUILD_TOOLS_WITH= -@set LOCATION= -@set REBUILD_TOOLS= -@set SVN_PULL= -@set SRC_CONF= -@set ARGUMENT= -@set SCRIPT=EDKSETUP_BAT - -@if not defined ORIGINAL_PATH set "ORIGINAL_PATH=%PATH%" -@REM Always set the WORKSPACE environment variable to the current directory -@if not defined WORKSPACE ( - @set "WORKSPACE=%CD%" -) -@if not exist "%BASE_TOOLS_PATH%" ( - @if exist "%WORKSPACE%\BaseTools" ( - set "BASE_TOOLS_PATH=%WORKSPACE%\BaseTools" - ) else ( - @if defined PACKAGES_PATH ( - @for %%i IN (%PACKAGES_PATH%) DO ( - @if exist %%~fi\BaseTools ( - @set BASE_TOOLS_PATH=%%~fi\BaseTools - @goto checkBaseTools - ) - ) - ) - ) -) -:checkBaseTools -@if not defined BASE_TOOLS_PATH ( - @echo. - @echo !!! ERROR !!! The BaseTools Package was not found !!! - @echo. - @goto ExitFailure -) -@if not exist "%WORKSPACE%\Conf" @mkdir "%WORKSPACE%\Conf" - -@@if not defined EDK_TOOLS_PATH @set "EDK_TOOLS_PATH=%BASE_TOOLS_PATH%" - -@REM Keep the existing EDK_TOOLS_PATH value, the --reset flag will set it -@REM back to WORKSPACE\BaseTools while the --location DIRECTORY flag will -@REM still take precedence if the location option follows the reset option -@REM on the command line. -@if defined EDK_TOOLS_PATH @set "LOCATION=%EDK_TOOLS_PATH%" - -:parse_cmd_line -@if "%1"=="" @goto MainRoutine -@if /I "%1"=="-h" @goto Usage -@if /I "%1"=="--help" @goto Usage -@if /I "%1"=="/?" @goto Usage -@if /I "%1"=="--version" @goto Version - -@REM These options will reset the system environment -@if /I "%1"=="-r" ( - @setlocal EnableDelayedExpansion - @set "WORKSPACE=%CD%" - @set "EDK_TOOLS_PATH=%CD%\BaseTools" - @set "LOCATION=!EDK_TOOLS_PATH!" - @endlocal - @shift - @goto parse_cmd_line -) -@if /I "%1"=="--reset" ( - @set "WORKSPACE=%CD%" - @set "EDK_TOOLS_PATH=%WORKSPACE%\BaseTools" - @set "LOCATION=%WORKSPACE%\BaseTools" - @shift - @goto parse_cmd_line -) - -@REM This option is used to overwrite the Conf/*.txt files with the -@REM WORKSPACE\BaseTools\Conf\*.template files. -@if /I "%1"=="--reconfig" ( - @set RECONFIG=TRUE - @shift - @goto parse_cmd_line -) - -@REM This option can be used to set the EDK_TOOLS_PATH containing the Win32 binaries to an -@REM alternate directory -@if /I "%1"=="--edk-tools-path" ( - @setlocal EnableDelayedExpansion - @set ARGUMENT=%2 - @if "!ARGUMENT:~0,2!"=="--" ( - @echo. - @echo ERROR : The --edk-tools-path flag requires an argument - @echo. - @endlocal - @goto Usage - ) - @endlocal - @set "LOCATION=%WORKSPACE%\%2" - @shift - @shift - @goto parse_cmd_line -) - -@REM Force pulling updated (or checkout if they do not exist) from SVN for the BaseTools\Bin\Win32 directory -@REM or the directory pointed to by the --location option -@if /I "%1"=="--pull" ( - @if "%REBUILD_TOOLS%"=="TRUE" ( - @echo. - @echo ERROR: The --pull option may not be used with the --rebuild option - @shift - @goto ExitFailure - ) - @set SVN_PULL=TRUE - @setlocal EnableDelayedExpansion - @set ARGUMENT=%2 - @if not "!ARGUMENT:~0,2!"=="--" ( - @endlocal - @set "LOCATION=%2" - @shift - ) - @shift - @goto parse_cmd_line -) - -@REM This options forces rebuilding the tools (provided the required tools are available -@if /I "%1"=="--rebuild" ( - @if "%SVN_PULL%"=="TRUE" ( - @echo. - @echo ERROR: The --reset option may not be used with the --pull option - @shift - @goto ExitFailure - ) - @set REBUILD_TOOLS=TRUE - @setlocal EnableDelayedExpansion - @set ARGUMENT=%2 - @if not "!ARGUMENT:~0,2!"=="--" ( - @endlocal - @set "LOCATION=%2" - @shift - ) - @shift - goto parse_cmd_line -) - -@REM This option will try to set the compiler environment for building Nt32Pkg/Nt32Pkg.dsc -@REM If the compiler environment is already installed, then no additional work is required. -@if /I "%1"=="--nt32" ( - @set NT32PKG=TRUE - @if not defined BUILD_TOOLS_WITH ( - @set BUILD_TOOLS_WITH=Latest - ) - @REM This option will try to set the environment for building the Nt32Pkg/Nt32Pkg; on a 64-bit - @REM Windows OS - @if /I "%2"=="X64" ( - @set NT32_X64=TRUE - @shift - ) - @shift - @goto parse_cmd_line -) - -@if not "%1"=="" goto UnknownOptionOrArgument -@goto MainRoutine - -:Usage -@echo Usage: %SCRIPT_NAME% [Options] -@echo Copyright(c) 2014, Intel Corporation. All rights reserved. -@echo. -@echo The system environment variable, WORKSPACE, is always set to the current -@echo working directory. -@echo. -@echo Options: -@echo --help, -h Print this help screen and exit. -@echo. -@echo --version Print this script's version and exit. -@echo. -@echo --reset, -r Reset the EDK_TOOLS_PATH and PATH system environment -@echo variables. The EDK_TOOLS_PATH default is -@echo WORKSPACE\BaseTools, however, it may be overridden by -@echo arguments given to the --edk-tools-path, --pull and/or -@echo --rebuild options. -@echo Once set, the EDK_TOOLS_PATH environment variable reset -@echo by opening up a new command prompt window or through one -@echo of the options provided by this tool -@echo. -@echo --reconfig Overwrite the WORKSPACE/Conf/*.txt files with the -@echo template files from the BaseTools/Conf directory. -@echo. -@echo --edk-tools-path DIRECTORY -@echo This option sets the EDK_TOOLS_PATH to the DIRECTORY -@echo value instead of the default (WORKSPACE\BaseTools). -@echo. -@echo --nt32 [X64] If a compiler tool chain is not available in the -@echo environment, call a script to attempt to set one up. -@echo This flag is only required if building the -@echo Nt32Pkg/Nt32Pkg.dsc system emulator. -@echo If the X64 argument is set, and a compiler tool chain is -@echo not available, attempt to set up a tool chain that will -@echo create X64 binaries. Setting these two options have the -@echo potential side effect of changing tool chains used for a -@echo rebuild. -@echo. -@pause -@echo. -@echo --pull [DIRECTORY] Get the EDK II BaseTools binaries from source control -@echo (must not be used with --rebuild). -@echo If the optional DIRECTORY argument is specified, the tool -@echo sets EDK_TOOLS_PATH to DIRECTORY. -@echo If the DIRECTORY argument is not specified, the tools are -@echo placed in the directory tree pointed to by the current -@echo EDK_TOOLS_PATH environment variable. If the binaries -@echo cannot be obtained from source control, the -@echo EDK_TOOLS_PATH will be set to the default, -@echo WORKSPACE\BaseTools directory. -@echo. -@echo --rebuild [DIRECTORY] -@echo Force Rebuilding the EDK II BaseTools from source -@echo (must not be used with --pull). -@echo NOTE: The build will use whatever compiler tool set -@echo is available in the environment prior to -@echo running edksetup.bat. -@echo If the optional DIRECTORY argument is specified, the tool -@echo sets EDK_TOOLS_PATH to DIRECTORY. Tools binaries will be -@echo placed in the appropriate subdirectory in the -@echo EDK_TOOLS_PATH directory. If the build fails, the -@echo EDK_TOOLS_PATH will be set to the default, -@echo WORKSPACE\BaseTools directory. -@goto ExitSuccess - -:Version -@echo %SCRIPT_NAME% Version: %SCRIPT_VERSION%%SVN_REVISION:~11,-1% -@echo Copyright(c) 2014, Intel Corporation. All rights reserved. -@set HIDE_PATH=TRUE -@call "%BASE_TOOLS_PATH%\Scripts\ShowEnvironment.bat" -@set HIDE_PATH= -@goto ExitSuccess - -:UnknownOptionOrArgument -@echo. ERROR : This argument is not valid: %1 -@echo. -@goto ExitFailure - -:NoVisualStudio -@echo ERROR : Unable to determine if a compiler tool chain has been enabled in this -@echo command-prompt window. Rebuilding of the tools with this script is not -@echo possible. -@echo Refer to the BaseTools\BuildNotes.txt for directions for building -@echo the BaseTools binaries. -@echo. -@goto ExitFailure - -:NoPython -@echo ERROR : Unable to rebuild the BaseTools binaries, python does not appear to be -@echo installed. If python is installed, please set the environment -@echo variable, PYTHONHOME to the Path to the python.exe, for example, -@echo if python.exe is located in the C:\Python27 directory, then: -@echo set PYTHONHOME=C:\Python27 -@echo. -@goto ExitFailure - -:BadPython -@echo ERROR : Unable to rebuild the BaseTools binaries, python does not appear to be -@echo installed. -@echo The python executable was not found in the PYTHONHOME: %PYTHONHOME% -@echo If python is installed, please set the environment variable, PYTHONHOME -@echo to the Path that contains python.exe, for example, if python.exe is -@echo located in the C:\Python27 directory, then: -@echo set PYTHONHOME=C:\Python27 -@echo. -@goto ExitFailure - -:NoCxFreeze -@echo ERROR : Unable to locate cx_Freeze 4.2.3. The cxfreeze.bat file must be located -@echo in the %PYTHONHOME%\Scripts directoryin order to rebuild the BaseTools -@echo binaries. -@echo. -@goto ExitFailure - -:NoBaseTools -@echo ERROR: Unable to locate the BaseTools directory containing the Source tree -@echo. -@goto ExitFailure - -@REM ######################################################################################### -@REM MAIN ROUTINE -@REM Set up the Build System environment -@REM ######################################################################################### -:MainRoutine -@if defined LOCATION @set "EDK_TOOLS_PATH=%LOCATION%" -@REM SET the EDK_TOOLS_PATH. -@if not exist "%EDK_TOOLS_PATH%" ( - @mkdir %EDK_TOOLS_PATH% -) -@if not defined NASM_PREFIX ( - @echo. - @echo WARNING : NASM_PREFIX environment variable is not set - @if exist "C:\nasm\nasm.exe" @set "NASM_PREFIX=C:\nasm\" - @if exist "C:\nasm\nasm.exe" @echo Found nasm.exe, setting the environment variable to C:\nasm\ - @if not exist "C:\nasm\nasm.exe" echo Attempting to build modules that require NASM will fail. -) -@REM Set up the path to include the EDK_TOOLS_PATH\Bin\Win32 directory; this test determines -@REM whether the path is in the workspace or a fully qualified path that may be outside of -@REM the workspace -@if exist "%WORKSPACE%\%EDK_TOOLS_PATH%" @set "EDK_TOOLS_PATH=%WORKSPACE%\%EDK_TOOLS_PATH%" - -@if defined REBUILD_TOOLS goto SetConf -@if defined SVN_PULL goto SetConf -@if not exist "%EDK_TOOLS_PATH%\Bin\Win32\build.exe" ( - @echo ERROR : %EDK_TOOLS_PATH%\Bin\Win32\build.exe does not exist - @echo Re-run this script using --reset, --pull or --rebuild - @echo. - @goto ExitFailure -) -@echo. -@echo Rebuilding of the tools is not required. Binaries of the latest, -@echo tested versions of the tools have been tested and included in the -@echo EDK II repository. -@echo. -@echo If you really want to build the tools, use the --rebuild option. -@echo. -@if not defined CYGWIN_HOME @echo "!!! WARNING !!! No CYGWIN_HOME set, gcc build may not be used !!!" -@if not defined CYGWIN_HOME @echo. -@REM Make sure the WORKSPACE\Conf directory contains the required text files that will be -@REM copied or replaced from the WORKSPACE\BaseTools\Conf directories' template files. -:SetConf -@if not exist "%EDK_TOOLS_PATH%\Conf" ( - @if exist "%BASE_TOOLS_PATH%\Conf" ( - @set "SRC_CONF=%BASE_TOOLS_PATH%\Conf" - ) -) else ( - @set "SRC_CONF=%EDK_TOOLS_PATH%\Conf" -) -@if not defined SRC_CONF ( - @echo ERROR : Unable to locate the BaseTools directory tree - @goto ExitFailure -) - -@REM The script will test to see if the files exist, and also use the RESET_ENVIRONMENT flag -@REM to overwrite the WORKSPACE\Conf *.txt files. -@call "%BASE_TOOLS_PATH%\Scripts\ShowEnvironment.bat" -@if errorlevel 1 ( - @echo Unable to copy the template files from "%SRC_CONF%" to "%WORKSPACE%\Conf" - @goto ExitFailure -) -@set SRC_CONF= - -@REM Set up Visual Studio if required to build the Nt32Pkg/Nt32Pkg.dsc emulator -@if "%NT32PKG%"=="TRUE" ( - @if not defined VSINSTALLDIR @set "PATH=%ORIGINAL_PATH%" - @if not defined NT32_X64 @call "%BASE_TOOLS_PATH%\get_vsvars.bat" - @if defined NT32_X64 call "%BASE_TOOLS_PATH%\Scripts\SetVisualStudio.bat" -) -@if "%NT32PKG%"=="TRUE" ( - @if not defined VS_PATH set "VS_PATH=%PATH%" -) -@if defined VS_PATH @set "PATH=%VS_PATH%" -@if not defined VS_PATH @set "PATH=%ORIGINAL_PATH%" -@if not defined EDK_TOOLS_BIN ( - @if exist %EDK_TOOLS_PATH%\Bin\Win32 ( - @set EDK_TOOLS_BIN=%EDK_TOOLS_PATH%\Bin\Win32 - ) else ( - @echo. - @echo !!! ERROR !!! Cannot find BaseTools Bin Win32!!! - @echo Please check the directory %EDK_TOOLS_PATH%\Bin\Win32 - @echo Or configure EDK_TOOLS_BIN env to point Win32 directory. - @echo. - @goto ExitFailure - ) -) -@set "PATH=%EDK_TOOLS_BIN%;%PATH%" - -@if "%REBUILD_TOOLS%"=="TRUE" @goto Rebuild -@if "%SVN_PULL%"== "TRUE" ( - if defined PYTHONHOME ( - @REM Use the python script if possible to test is the svn command is available, if it fails, the user may be - @REM able to rebuild the Win32 binaries - @call "%BASE_TOOLS_PATH%\Scripts\UpdateBuildVersions.py" --svn-test -v - @if errorlevel 1 ( - @echo ERROR : The command-line svn tool is not available and the Win32 binaries do not exist - @echo Please re-run this script again with the --rebuild option to attempt to build - @echo the binaries - @echo. - @goto ExitFailure - ) - @if exist %EDK_TOOLS_PATH%\Bin\Win32 @rmdir /S /Q %EDK_TOOLS_PATH%\Bin\Win32 - @call svn co https://svn.code.sf.net/p/edk2-toolbinaries/code/trunk/Win32 "%EDK_TOOLS_PATH%\Bin\Win32" - ) else ( - @call svn co https://svn.code.sf.net/p/edk2-toolbinaries/code/trunk/Win32 "%EDK_TOOLS_PATH%\Bin\Win32" - @if errorlevel 1 ( - @echo ERROR : The command-line svn tool is not available and the Win32 binaries do not exist - @echo Python does not appear to be available either. This script cannot be used to - @echo build the Win32 binaries or to obtain them from this repository: - @echo https://svn.code.sf.net/p/edk2-toolbinaries/code/trunk/Win32 - @goto ExitFailure - ) - ) - @goto ShowAndExit -) - -@if not "%REBUILD_TOOLS%"=="TRUE" @goto ShowAndExit - -@REM The following code is used to rebuild the Win32 BaseTools binaries - check that required tools are available -:Rebuild -@if not exist "%BASE_TOOLS_PATH%\Source" @goto NoBaseTools -@endlocal -@if not defined VCINSTALLDIR @goto NoVisualStudio -@if not defined PYTHONHOME @goto NoPython -@if not exist "%PYTHONHOME%\python.exe" @goto BadPython -@REM python.exe has been located, now make sure it's in the PATH -@call python --version > nul 2>&1 -@if errorlevel 1 @set "PATH=%PYTHONHOME%\python.exe;%PATH%" -@if not defined PYTHON_FREEZER_PATH ( - @if not exist "%PYTHONHOME%\Scripts\cxfreeze.bat" @goto NoCxFreeze - @set "PYTHON_FREEZER_PATH=%PYTHONHOME%\Scripts" -) -@call "%BASE_TOOLS_PATH%\Scripts\SetVisualStudio.bat" -@if errorlevel 1 @goto ExitFailure - -:ShowAndExit -@call "%BASE_TOOLS_PATH%\Scripts\ShowEnvironment.bat" - -@REM ######################################################################################### -@REM EXIT ROUTINES -@REM ######################################################################################### -:ExitSuccess -@set SCRIPT_NAME= -@set SCRIPT_VERSION= -@set SVN_REVISION= -@set RESET_ENVIRONMENT= -@set RECONFIG= -@set NT32PKG= -@set BUILD_TOOLS_WITH= -@set LOCATION= -@set REBUILD_TOOLS= -@set SVN_PULL= -@set SRC_CONF= -@set ARGUMENT= -@set SCRIPT= -@set LIST_VS_VERSIONS= -@set PYTHON_FREEZER_PATH= -@echo on -@exit /B 0 - -:ExitFailure -@set SCRIPT_NAME= -@set SCRIPT_VERSION= -@set SVN_REVISION= -@set RESET_ENVIRONMENT= -@set RECONFIG= -@set NT32PKG= -@set BUILD_TOOLS_WITH= -@set LOCATION= -@set REBUILD_TOOLS= -@set SVN_PULL= -@set SRC_CONF= -@set ARGUMENT= -@set SCRIPT= -@set LIST_VS_VERSIONS= -@set PYTHON_FREEZER_PATH= -@echo on -@exit /B 1 diff --git a/Maintainers.txt b/Maintainers.txt deleted file mode 100644 index 05e6e39b3d..0000000000 --- a/Maintainers.txt +++ /dev/null @@ -1,221 +0,0 @@ -EDK II Maintainers -================== - -This file provides information about the primary maintainers for -EDK II. - -In general, you should not privately email the maintainer. You should -email the edk2-devel list, but you can also Cc the maintainer. - -Descriptions of section entries: - - L: Mailing list that is relevant to this area (default is edk2-devel) - Patches and questions should be sent to the email list. - M: Cc address for patches and questions (ie, the package maintainer) - W: Web-page with status/info - T: SCM tree type and location. Type is one of: git, svn. - S: Status, one of the following: - Supported: Someone is actually paid to look after this. - Maintained: Someone actually looks after it. - Odd Fixes: It has a maintainer but they don't have time to do - much other than throw the odd patch in. See below. - Orphan: No current maintainer [but maybe you could take the - role as you write your new code]. - Obsolete: Old code. Something tagged obsolete generally means - it has been replaced by a better system and you - should be using that. - -EDK II ------- -W: http://www.tianocore.org/edk2/ -L: https://lists.sourceforge.net/lists/listinfo/edk2-devel -T: git - https://github.com/tianocore/edk2.git -T: git (mirror) - https://bitbucket.org/tianocore/edk2.git -T: git (mirror) - http://git.code.sf.net/p/tianocore/edk2 -T: svn (read-only, deprecated) - https://svn.code.sf.net/p/edk2/code/trunk/edk2 - -Responsible Disclosure, Reporting Security Issues -------------------------------------------------- -W: https://github.com/tianocore/tianocore.github.io/wiki/Security - -EDK II Releases: ----------------- -UDK2014 -W: http://www.tianocore.org/udk2014/ -S: Supported - -EDK II Packages: ----------------- -AppPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/AppPkg -M: Daryl McDaniel -M: Jaben Carsey - -ArmPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/ArmPkg -M: Leif Lindholm -M: Ard Biesheuvel - -ArmPlatformPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/ArmPlatformPkg -M: Leif Lindholm -M: Ard Biesheuvel - -ArmVirtPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/ArmVirtPkg -M: Laszlo Ersek -M: Ard Biesheuvel - -BaseTools -W: https://github.com/tianocore/tianocore.github.io/wiki/BaseTools -M: Yonghong Zhu -M: Liming Gao - -BeagleBoardPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/BeagleBoardPkg -M: Leif Lindholm -M: Ard Biesheuvel - -CorebootModulePkg, CorebootPayloadPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/Coreboot_UEFI_payload -M: Maurice Ma -M: Prince Agyeman -S: Maintained - -CryptoPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/CryptoPkg -M: Qin Long -M: Ting Ye - -DuetPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/DuetPkg -M: Ruiyu Ni - -EdkCompatibilityPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/EdkCompatibilityPkg -M: Liming Gao - -EdkShellPkg, EdkShellBinPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/EdkShellPkg -M: Ruiyu Ni -T: svn - https://svn.code.sf.net/p/efi-shell/code/trunk/Shell/ -S: Obsolete (Use ShellPkg & ShellBinPkg instead) - -EmbeddedPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/EmbeddedPkg -M: Leif Lindholm -M: Ard Biesheuvel - -EmulatorPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/EmulatorPkg -M: Jordan Justen -M: Andrew Fish -S: Maintained - -FatPkg, FatBinPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/Edk2-fat-driver -M: Ruiyu Ni -T: svn - https://svn.code.sf.net/p/edk2-fatdriver2/code/trunk/EnhancedFat -T: git - https://github.com/tianocore/edk2-FatPkg.git - -IntelFrameworkModulePkg -W: https://github.com/tianocore/tianocore.github.io/wiki/IntelFrameworkModulePkg -M: Jeff Fan - -IntelFrameworkPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/IntelFrameworkPkg -M: Michael D Kinney -M: Jeff Fan - -IntelFspPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/IntelFspPkg -M: Jiewen Yao - -IntelFspWrapperPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/IntelFspWrapperPkg -M: Jiewen Yao - -MdeModulePkg -W: https://github.com/tianocore/tianocore.github.io/wiki/MdeModulePkg -M: Feng Tian -M: Star Zeng - -MdePkg -W: https://github.com/tianocore/tianocore.github.io/wiki/MdePkg -M: Michael D Kinney -M: Liming Gao - -NetworkPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/NetworkPkg -M: Siyuan Fu -M: Jiaxin Wu - -Nt32Pkg -W: https://github.com/tianocore/tianocore.github.io/wiki/Nt32Pkg -M: Ruiyu Ni - -Omap35xxPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/Omap35xxPkg -M: Leif Lindholm -M: Ard Biesheuvel - -OptionRomPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/OptionRomPkg -M: Ruiyu Ni - -OvmfPkg -W: http://www.tianocore.org/ovmf/ -M: Jordan Justen -M: Laszlo Ersek -S: Maintained - -PcAtChipsetPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/PcAtChipsetPkg -M: Ruiyu Ni - -PerformancePkg -W: https://github.com/tianocore/tianocore.github.io/wiki/PerformancePkg -M: Daryl McDaniel -M: Jaben Carsey - -SecurityPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/SecurityPkg -M: Chao Zhang - -ShellBinPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/ShellPkg -M: Jaben Carsey (Ia32/X64) -M: Shumin Qiu (Ia32/X64) -M: Leif Lindholm (ARM/AArch64) -M: Ard Biesheuvel (ARM/AArch64) - -ShellPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/ShellPkg -M: Jaben Carsey -M: Shumin Qiu - -SourceLevelDebugPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/SourceLevelDebugPkg -M: Jeff Fan -M: Hao Wu - -StdLib, StdLibPrivateInternalFiles -W: https://github.com/tianocore/tianocore.github.io/wiki/StdLib -M: Daryl McDaniel -M: Jaben Carsey - -UefiCpuPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/UefiCpuPkg -M: Jeff Fan - -UnixPkg -W: https://github.com/tianocore/tianocore.github.io/wiki/UnixPkg -S: Obsolete (Use EmulatorPkg instead) - -Vlv2DeviceRefCodePkg -M: David Wei -M: Tim He - -Vlv2TbltDevicePkg -M: David Wei -M: Tim He -- cgit v1.2.3