On 10/27/2014 11:27 AM, Hauch, Larry wrote: > Actually, ORIGINAL_PATH is not a local variable, but is used as a flag so > that when Edk2Setup (or edksetup) is run multiple times in the same command > prompt window, the EDK II BaseTools path does not get added more than one > time, along with other changes to the PATH. > The design allowed for using Edk2Setup once with --nt32 for including visual > studio tools, then run it a second time without the flag and the visual > studio tools would be cleared from the PATH.
Thanks. It would be nice if we could avoid changing the calling environment - could we require the user to already be running a VS Command Prompt for whichever version of Visual C++ they want to use, since Visual Studio installs shortcuts which set up the environment? Also, I see in SetVisualStudio.bat that it sets a COMMONTOOLSx64 variable: could it set the path to %VSxxCOMNTOOLS%\..\..\VC and then call "%COMMONTOOLSx64%\vcvarsall.bat x86_amd64" to avoid the hard-coded paths? Will the error message under the VersionNotFound label work? I don't see any parameters being passed from Edk2Setup.bat - in particular, BUILD_TOOLS_WITH appears unused. -- Bruce ------------------------------------------------------------------------------ _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
