#622 Static Libraries not rebuilt if Static Library dependency is rebuilt

[Martin Turski]

If I add a static library project dependency A on static library project B and rebuild A, then it does not trigger an automatic rebuild of B. Because static library project B embeds the static library of A as dependency and B is not rebuilt, the changes in the new library A do not affect application C that depends on B.

[Teodor Petrov]

C::B's build system doesn't support embedding one static lib in another.
You've to link application C with both libraries A and B, then it will work.

[Andrew Cottrell]

From Teodor's post above I think this ticket can be closed.

[Martin Turski]

I would like to point out that C++ modules are going into the same direction as my original report. In technical ways the dependency resolution is possible across static library boundaries aswell. Thus my suggestion would strengthen the product in the future.

[Morten MacFly]

Are you aware that you already can setup static libs as an external dependancy that enforce a re-link once it has been changed? Isn't this what you want? This would work for any type of files, btw...

[Andrew Cottrell]

From Morten's post above I think this ticket can be closed.

[Andrew Cottrell]

Another ticket IMHO that can be closed.