[CMake] cyclic DLL dependencies
Michael Wild
themiwi at gmail.com
Fri Mar 14 05:26:52 EDT 2008
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 13Mar, 2008, at 17:21, Andy Lego wrote:
> Hello Michael,
>
> You can also try co cleanup the API so you don't need the circular
> dependency. This way you can still keep the library separate, but at
> the same time reduce problems in the future.
>
> Andy
True. Ultimately this would be the only true solution. But currently
it is plain impossible as I have to remain compatible to legacy stuff.
>
>
> On Thu, Mar 13, 2008 at 9:18 AM, Michael Wild <themiwi at gmail.com>
> wrote:
>>
>> On 13Mar, 2008, at 15:56, David Cole wrote:
>>
>>> The real solution is to make them into one library. If you can't
>>> have one without the other, then why bother having two? You have to
>>> have both by definition because of the two-way dependency. Why not
>>> consolidate them into one?
>>>
>>> Or... force them to be static libs (ADD_LIBRARY(... STATIC ...)) and
>>> link them both everywhere they need to be linked...
>>
>>
>> Thanks
>>
>> But this is not possible. As I said, the smaller of the libraries
>> must
>> be exchangeable. And multiple versions of a merged library is just a
>> no-go.
>>
>> Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAkfaRN0ACgkQyAe0BK8NufNhNwCfcsT622wRPvA5RdjMb0Ci+yy1
OnwAn10RQkd+r2MuINJVz3Zlje61LI2+
=4qVL
-----END PGP SIGNATURE-----
More information about the CMake
mailing list