[Scons-dev] Tool initialization is called twice
Bill Deegan
bill at baddogconsulting.com
Wed May 28 17:43:46 EDT 2014
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?
-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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://two.pairlist.net/pipermail/scons-dev/attachments/20140528/d27269c9/attachment.html>
More information about the Scons-dev
mailing list