[Scons-users] Dependencie with Sconscripts and builder's environment

[Albert Arquer]

Hello there

We use scons intensively in our team to build our deliverables. We have
many many sconscripts and we found out that we had to explicitly tell scons
that a particular target depends upon those sconscripts
self.env.Depends(target, scons_sources...).

The reason for this is that while many times modification of our
sconscripts are automatically caught by scons (because they have an impact
in the dependency tree) other changes might be more subtle, for examples
those changes which only modify a builder's environment.
Ideally we would expect scons to detect changes in the builder's
environment and realize the target generated by that builder is out-dated,
however this is not what we have seen.. If a builder's env changes but no
other dependencies or target/sources change, scons still says the target is
up to date...

Is this a known limitation of scons? if so, is there any workaround besides
the one I already stated? or are we going about this all wrong?

I find this weird as I have never seen any examples where a scons target
was explicitly registered as dependent on the Sconscript which declared the
target, so that makes me suspect there might be a better way to do this...

Also another weird thing is that I have noticed scons is capable of
detecting when a particular builder has changed, as is capable of isolating
that change to the targets that actually use that builder, so why not
compute the builder's signature combined with the environment?

Thanks,
Albert.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20161011/2fc43747/attachment.html>