[Scons-dev] Checking for bad build commands

Tom Tanner (BLOOMBERG/ LONDON) ttanner2 at bloomberg.net
Thu Mar 28 07:23:01 EDT 2013


I had a situation recently where I spotted derived objects weren't being copied from the cache for a particular object, and it turned out that the command line being used had a full path to the script, rather than a relative one.

OK, it's not surprising that given that situation, scons does what it does, but I was wondering if there was an easier way to spot this. Currently I've got a small change in get_cachedir_bsig in Node/FS.py that checks executor.get_contents() doesn't include a reference to the NFS mount where we have our git clones, but that's not very clean to say the least, and obviously won't trap when people do development somewhere else.

So, is there a better way to check this? And if so, what?


More information about the Scons-dev mailing list