[CMake] Resolving static lib dependency at executable link time

[Leif Walsh]

I think you shouldn't make B depend on anything, and just make sure that you list all the libs you need at executable link time. 

Sent from my iPhone

On Feb 25, 2013, at 7:47, Pierre Mallard <mallard.pierre at gmail.com> wrote:

> Well it is indeed possible and it works... Note that static libraries 's object files are built with unresolved symbols. Final resolution is performed when building executable
> Therefore libB can compile without libC and conversely ...
> Anyone else ?
> 
> 
> 
> On Mon, Feb 25, 2013 at 12:23 PM, Ansis Māliņš <ansis.malins at gmail.com> wrote:
>> >libB depends on libC and libC depends on libB.
>> How is that even possible? You compile B and it fails because there's no C yet. You compile C and it fails because there's no B yet.
> 
> --
> 
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20130225/6f4f12e4/attachment.htm>