Re: Clone effectiveness

Fully agree.

My approach is that I have a keyword parameter from the command line
to chose which target to build and then only the pattern-matched
builds are actually created, essentially only one env is created. I do
it only because I want to avoid the initial startup latency ... if
your env is not conditionally created or for a built that really have
many clones then bad luck. Of course it would definitely be great if
the we cannot feel the existence of scons's runtime.
On Tue, Sep 18, 2018 at 4:31 PM Pierre-Luc Boily
<[email protected]> wrote:
>
> I agree 15 seconds is not a lot compare to the whole.  But when doing
> iterative build, 15 seconds it's a lot!  At least we have the --interactive
> as a good work around (on unix).
>
> So, beside having longer tree creation with many Clone, could this lead to
> other problems?  Is it better to avoid Clone where I can?
>
>
> Mats Wichmann wrote
> >>>15 seconds is slow, but if I sped up the sconscript time by 50%, I'd
> >>>still make no more than a 2% impact on the overall time.
>
>
>
>
>
> --
> Sent from: http://scons.1086193.n5.nabble.com/Users-f16930.html
> _______________________________________________
> Scons-users mailing list
> [email protected]
> https://pairlist4.pair.net/mailman/listinfo/scons-users
_______________________________________________
Scons-users mailing list
[email protected]
https://pairlist4.pair.net/mailman/listinfo/scons-users