[Scons-dev] Tool initialization is called twice
anatoly techtonik
techtonik at gmail.com
Thu May 29 02:50:48 EDT 2014
On Thu, May 29, 2014 at 12:43 AM, Bill Deegan <bill at baddogconsulting.com>wrote:
> Gary,
>
> I was under the impression (need to check the code), that you could do:
> DefaultEnvironment(tools=[]) in SConstruct and it would prevent any tools
> from being initialized and speed SCons startup.
>
> Did I misunderstand?
>
No, that's correct.
https://stackoverflow.com/questions/15205210/prevent-scons-from-looking-for-standard-tools#comment21499852_15206709
> -Bill
>
>
> On Wed, May 28, 2014 at 5:40 AM, Gary Oberbrunner <garyo at oberbrunner.com>wrote:
>
>>
>>
>>
>> On Wed, May 28, 2014 at 3:39 AM, anatoly techtonik <techtonik at gmail.com>wrote:
>>
>>> Hi,
>>>
>>> I found that SCons calls tool initialization twice for this simple
>>> SConstruct:
>>>
>>> env = Environment()
>>> env.Program(target='flite', source=[])
>>>
>>
>> Right, this is one of the things I want to address with the toolchain
>> revamp. DefaultEnvironment is constructed before the SConstruct is read,
>> and all the default tools are detected there.
>>
>> Environment() is distinct from DefaultEnvironment(); DefaultEnvironment
>> is _only_ used for plain Object(), Program() etc. calls. This is by
>> design. Environment() does not inherit changes in DefaultEnvironment().
>>
>> --
>> Gary
>>
>> _______________________________________________
>> Scons-dev mailing list
>> Scons-dev at scons.org
>> http://two.pairlist.net/mailman/listinfo/scons-dev
>>
>>
>
> _______________________________________________
> Scons-dev mailing list
> Scons-dev at scons.org
> http://two.pairlist.net/mailman/listinfo/scons-dev
>
>
--
anatoly t.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://two.pairlist.net/pipermail/scons-dev/attachments/20140529/4d5d1831/attachment.html>
More information about the Scons-dev
mailing list