[Scons-users] env.Command and _process_ environment variables :-(
Pedro Larroy
pedro.larroy.lists at gmail.com
Wed Oct 17 11:55:29 EDT 2012
I'm thinking it could be a windows 7 bug, we could warn in the
documentation. I spent quite some hours figuring this one out.
Pedro.
On Wed, Oct 17, 2012 at 5:54 PM, Pedro Larroy
<pedro.larroy.lists at gmail.com> wrote:
> Tried that, doesn't work also.
>
>
> Pedro.
>
> On Tue, Oct 16, 2012 at 8:44 PM, Gary Oberbrunner <garyo at oberbrunner.com> wrote:
>>
>>
>> On Tue, Oct 16, 2012 at 2:19 PM, Pedro Larroy <pedro.larroy.lists at gmail.com>
>> wrote:
>>>
>>> Hi
>>>
>>> I reproduced with a minimal setup. I think it's a bug, see the
>>> attached zip file. When executing run.bat the two environments
>>> differ, the one that is displayed by show.py lacks VS11 related stuff
>>> in the PATH.
>>>
>>> https://www.dropbox.com/sh/h6c8w3wjnfw5z6i/tAEBi2eHuE/path.zip
>>>
>>> Should I fill a ticket?
>>
>>
>> I'm not sure. Try this: after creating the Environment, reset env['ENV']
>> so:
>> env['ENV'] = os.environ
>> and see if it works then. It may be that the MSVC tool is bashing the env
>> after it gets set to os.environ.
>>
>> --
>> Gary
>>
>> _______________________________________________
>> Scons-users mailing list
>> Scons-users at scons.org
>> http://four.pairlist.net/mailman/listinfo/scons-users
>>
More information about the Scons-users
mailing list