[Scons-dev] debugging signatures

[Tom Tanner (BLOOMBERG/ LONDON)]

The other thing I'm not sure about is if I have a build script that says
   '$PERL -w ${SOURCES[1]} blah blah blah ${SOURCE.base}'

how much of that gets put into the the signature when it's being calculated.

----- Original Message -----
From: bill at baddogconsulting.com
To: TOM TANNER (BLOOMBERG/ LONDON), scons-dev at scons.org
At: Sep 19 2012 18:50:19

Tom,

Wouldn't grep'ing your SConstruct/SConscripts find this for you?

-Bill
On Sep 19, 2012, at 10:00 AM, TOM TANNER (BLOOMBERG/ LONDON) <ttanner2 at bloomberg.net> wrote:


> Due to not really paying attention when I was developing some of my scripts, I have some command lines that contain names with sort-of-absolute paths. That is to say its /dev/git/<username>/<projectname>/scripts/somescript 

> 

> Unsurprisiingly, this causes the build not to use the cached version from /dev/git/<someelses>/<project>/scripts/somescript

> 

> So I can see how I can fix this by using ${ scriptname $} and making sure scriptname is referenced as a dependency.

> 

> However, how can I find out how many places I've done this in? In particular, is there some why of printing the contents of an action when you're calculating the signature, so I can scan for ones that have /dev/git in them?

> 

> Thanks

> _______________________________________________

> Scons-dev mailing list

> Scons-dev at scons.org

> http://two.pairlist.net/mailman/listinfo/scons-dev