[Scons-users] 'MSVS' Environment variable contents
Andrew C. Morrow
andrew.c.morrow at gmail.com
Tue Feb 17 21:14:17 EST 2015
Thanks Dirk -
I will give it a look. I had avoided reaching into the internal Tool
methods as I assumed that those were not really part of the public SCons
API and could change across SCons releases.
I think we may have just ultimately hard-coded the SDK path, since in this
particular case we definitely know the install path of the SDK on the CI
system, and don't need this information in builds made elsewhere. Not
exactly elegant, but it seems like a reasonable compromise.
It might be nice to have this information exposed in a documented and
stable way though.
On Fri, Feb 13, 2015 at 5:06 PM, Dirk Bächle <tshortik at gmx.de> wrote:
> On 13.02.2015 04:24, Andrew C. Morrow wrote:
>> Unfortunately, not really. I actually need to know the path because I
>> want to access a file (that is neither a library nor a header)
>> that is bundled with the SDK. I simply want to copy that file somewhere
>> else, but I'd prefer to just re-use the detection that SCons
>> performs to locate the SDK. The PLATFORMSDKDIR would have been perfect,
>> but it seems it is not really an option.
> Have another look at "sdk.py" in Tool.MSCommon. The method
> get_default_sdk() should return the version/ID for the default SDK, and you
> could use that as key into Tool.MSCommon.InstalledSDKMap ... or pick some
> of the other provided methods/dicts.
> Scons-users mailing list
> Scons-users at scons.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Scons-users