This approach sounds like a big improvement: I've been wondering if the build system could use VSxxxCOMNTOOLS instead of hard-coding paths for a while. If not, we should at least be able to use the ProgramFiles and ProgramFiles(x86) environment variables instead.
-- Bruce On Fri, Sep 26, 2014 at 10:30 PM, Scott Duplichan <[email protected]> wrote: > A new batch file function is needed for setting up the build tool path > environment variables when a standard install of Visual Studio is used. > This batch function can derive the Visual Studio install directory from > the VSxxxCOMNTOOLS environment variable. The batch function can find the > proper rc.exe path by launching the command line build environment and > then checking the path to rc.exe. > > Nasm already has a path environment variable and a similar one can be > added for IASL.exe. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
