Hi Scott, We will not enable auto configuring the tool chain path for every calling of the edksetup.bat, developers with non-standard installations typically know more about compiler environments, so we allowed developers to modify the tools_def.txt file and our tools would not change it unless the developer forced it to be changed. Also the hard coding paths in tool_def are not only visual studio but others like WINDDK, ASL. We prefer a standalone tool to configure the paths for all tool chains in the future, but the work is low priority.
Thanks, Dennis -----Original Message----- From: Liu, Yingke D [mailto:[email protected]] Sent: Sunday, September 28, 2014 3:43 PM To: [email protected] Subject: Re: [edk2] [RFC] BaseTools: Avoid hard coding of Visual Studio path Scott, A very good suggestion. We will evaluate it first. Thanks. Dennis -----Original Message----- From: Bruce Cran [mailto:[email protected]] Sent: Sunday, September 28, 2014 4:22 AM To: [email protected] Subject: Re: [edk2] [RFC] BaseTools: Avoid hard coding of Visual Studio path 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 ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
