[Scons-users] dependencies when you define environment variables

[TOM TANNER (BLOOMBERG/ LONDON)]

On the whole, that (adding the thing to the builder /call/) is rather unfortunate as it means the client needs to know something of how the builder is implemented and it means if we replace a toolchain with another toolchain that behaves slightly differently we need to go and find all the clients thereof and replace the calls.

Yes, I know I'm being picky. But my experience is that little things like that can trip people up and cause embarassing problems later on down the line, and hiding 'implementation details' like that would seem to be a good thing to do.



----- Original Message -----
From: scons-users at scons.org
To: scons-users at scons.org
At:  7/18 15:05:01

On Wed, Jul 18, 2012 at 9:51 AM, TOM TANNER (BLOOMBERG/ LONDON)
<ttanner2 at bloomberg.net> wrote:

>> Well, your builder will also take env var overrides, so it's mostly not any

>> different from Command.

> It can?

>

> So I can do

> builder = Builder('something that requires env set',

>                   ENV = env['ENV'] + ( 'VARIABLENAME': '${SOURCE.dir}')

> ?

>

> (I realise that + is not the appropriate operator here)


No, the overrides are on the *call* to the builder, not when you create it.


>> I think what you're saying is having to manipulate env[ENV] before calling

>> the builder each time is annoying.  Is that right?

> That is true too

>

> _______________________________________________

> Scons-users mailing list

> Scons-users at scons.org

> http://four.pairlist.net/mailman/listinfo/scons-users




-- 
Gary
_______________________________________________
Scons-users mailing list
Scons-users at scons.org
http://four.pairlist.net/mailman/listinfo/scons-users