Libtool versioning of a library that depends on other libraries.

Posted by Artyom on Stack Overflow See other posts from Stack Overflow or by Artyom
Published on 2010-04-17T11:30:29Z Indexed on 2010/04/17 11:33 UTC
Read the original article Hit count: 322

Hello,

I have a framework that uses Boost and CgiCC in the core application and in its interface.

How should I version the library binary interface (a.k.a. libtool -version-info)?

I have no problems tracking the changes in library itself when I make various changes. As it is clear for me how should I version.

But...

Both Boost and CgiCC libraries do not provide any backward compatible API/ABI and my library may be linked with quite arbitrary versions Boost and CgiCC so I can't provide any promise about the interfaces, so I can't really specify -version-info because even the same library compiled against different versions of Boost and CgiCC would not be compatible.

So... What should I do? How should I version library?

I know that I should not depend on Boost and CgiCC interfaces in first place, but this is what I get so far for existing stable version. This issue is addressed in next major release but I still have and want to maintain current release as it is very valuable.

© Stack Overflow or respective owner

Related posts about libtool

Related posts about versioninfo