[CMake] Dealing with circular linker dependencies

2007-10-04 Thread Tal Blum
I have two c++ libraries each depending on the other which creates a circular linker dependency problem. Does anyone know how to solve this problem? If this is not possible to solve at the command-line level can someone tell me how I can write a ADD_CUSTOM_COMMAND or ADD_CUSTOM_TARGET that will

Re: [CMake] Dealing with circular linker dependencies

2007-10-04 Thread Juan Sanchez
Aside from rearchitecting your project. You need to place one library on both sides of the other library in the arguments to the linker. -l A -l B -l A This assures that the linker can resolve all the needed symbols. Juan Tal Blum wrote: I have two c++ libraries each depending on the other

Re: [CMake] Dealing with circular linker dependencies

2007-10-04 Thread David Cole
It's also *nearly/totally?* impossible for Windows dll builds, so if you ever intend to build them as dlls on Windows, rearchitect your project. Circular library dependencies are best avoided if at all possible. On 10/4/07, Juan Sanchez [EMAIL PROTECTED] wrote: Aside from rearchitecting your

Re: [CMake] Dealing with circular linker dependencies

2007-10-04 Thread Alexandru Ciobanu
Hi! I was able to build three circularly dependent libs with CMake. Still I strongly recommend listening to the advices of refactoring your code. If there is no other way around it here is what I have used. The procedure to follow ( on Linux ) where libfoo and libbar are the libraries you