Hi Folks,
I have added a new script, Edk2Setup.bat, to the edk2 trunk and three new
scripts in the BaseTools\Scripts directory, r15867.
The plan is to allow people to test this script through the end of September.
If there are no issues at that time, we can replace the existing edksetup.bat
with the content from this file (and the Edk2Setup.bat file will be removed).
After getting feedback from [RFC ] Proposed changes to edksetup.bat (23 July,
2014), the Edk2Setup.bat script now has the following option.
While the script does use the BaseTools\get_vsvar.bat script, I did not move
the script into the Scripts directory as stated in the RFC.
Also note that since the help text is now over 2, 24 line pages long, a pause
has been inserted after the first page has been displayed.
e:\edk2>edk2setup --help
Usage: edk2setup [Options]
Copyright(c) 2014, Intel Corporation. All rights reserved.
The system environment variable, WORKSPACE, is always set to the current
working directory.
Options:
--help, -h Print this help screen and exit.
--version Print this script's version and exit.
--reset, -r Reset the EDK_TOOLS_PATH and PATH system environment
variables. The EDK_TOOLS_PATH default is
WORKSPACE\BaseTools, however, it may be overridden by
arguments given to the --edk-tools-path, --pull and/or
--rebuild options.
Once set, the EDK_TOOLS_PATH environment variable reset
by opening up a new command prompt window or through one
of the options provided by this tool
--reconfig Overwrite the WORKSPACE/Conf/*.txt files with the
template files from the BaseTools/Conf directory.
--edk-tools-path DIRECTORY
This option sets the EDK_TOOLS_PATH to the DIRECTORY
value instead of the default (WORKSPACE\BaseTools).
--nt32 [X64] If a compiler tool chain is not available in the
environment, call a script to attempt to set one up.
This flag is only required if building the
Nt32Pkg/Nt32Pkg.dsc system emulator.
If the X64 argument is set, and a compiler tool chain is
not available, attempt to set up a tool chain that will
create X64 binaries. Setting these two options have the
potential side effect of changing tool chains used for a
rebuild.
Press any key to continue . . .
--pull [DIRECTORY] Get the EDK II BaseTools binaries from source control
(must not be used with --rebuild).
If the optional DIRECTORY argument is specified, the tool
sets EDK_TOOLS_PATH to DIRECTORY.
If the DIRECTORY argument is not specified, the tools are
placed in the directory tree pointed to by the current
EDK_TOOLS_PATH environment variable. If the binaries
cannot be obtained from source control, the
EDK_TOOLS_PATH will be set to the default,
WORKSPACE\BaseTools directory.
--rebuild [DIRECTORY]
Force Rebuilding the EDK II BaseTools from source
(must not be used with --pull).
NOTE: The build will use whatever compiler tool set
is available in the environment prior to
running edksetup.bat.
If the optional DIRECTORY argument is specified, the tool
sets EDK_TOOLS_PATH to DIRECTORY. Tools binaries will be
placed in the appropriate subdirectory in the
EDK_TOOLS_PATH directory. If the build fails, the
EDK_TOOLS_PATH will be set to the default,
WORKSPACE\BaseTools directory.
Larry Hauch
Intel Corporation
SSG, STO, Platform Software Infrastructure
2800 Center Dr.
DuPont, WA 98327
Work: (253) 371-8550
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
