[Scons-users] Propagating build failure to independent project

[Björn Pollex]

Hello SCons-community!

I am currently trying to find a solution for the following problem. Suppose
we have to projects, a library and an executable that links this library.
They are independent SCons projects, so I first build the library, and then
the executable. Now I change some internal implementation detail of the
library, and the next build will fail. The problem is, since I didn't do a
clean build (expensive), the old library binary is still in place, and the
next build of the executable will build against it!

In reality, I am working with these two projects in Eclipse CDT. I have a
project reference configured from the executable to the library. Now when I
work on the library and then want to build both projects in one step, I
will often run into the scenario described above. Since Eclipse does not
currently provide any way around that, I am trying to implement a solution
in SCons.

The problem is that there seems to be no way in SCons to execute a specific
instruction after the build of the library has failed, because after
failure, SCons will not update any downstream targets (this is also true
for Requires()).

Can anyone suggest a solution here?

Regards,

    Björn Pollex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://four.pairlist.net/pipermail/scons-users/attachments/20130805/85fae73c/attachment-0001.htm