[Scons-users] Propagating build failure to independent project

[Björn Pollex]

This would solve the issue, but there are problems with that approach.
First, the library is used in several different projects, but that could be
overcome. The main problem is that Eclipse expects a flat workspace layout.
While this is also a problem that can be solved, I would like to keep the
layout as it is right now.

Still, thanks for your input!

Regards,

    Björn Pollex


On Mon, Aug 5, 2013 at 5:18 PM, Dirk Bächle <tshortik at gmx.de> wrote:


>  Hi Björn,

>

> I'm not quite sure how "project references" work exactly in Eclipse CDT,

> but to me it seems to be very clear that your executable definitely depends

> on your library.

> So, from the SCons point of view, it would be better to have them both in

> a combined SConstruct, such that SCons always sees and constructs the full

> dependency tree (library + executable).

> In Eclipse you could then call either "scons your_lib_name" if you just

> want to update the library, or simply "scons" to rebuilt everything that

> has changed.

>

> This should make special "after-build-failure" actions superfluous,

> because the "scons" build will break automatically when the library can't

> be updated.

>

> Best regards,

>

> Dirk

>

>

> On 05.08.2013 16:20, Björn Pollex wrote:

>

>    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

>

>

> _______________________________________________

> Scons-users mailing listScons-users at scons.orghttp://four.pairlist.net/mailman/listinfo/scons-users

>

>

>

> _______________________________________________

> Scons-users mailing list

> Scons-users at scons.org

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

>

>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://four.pairlist.net/pipermail/scons-users/attachments/20130806/547f6b6c/attachment.html