On Thu, May 3, 2012 at 2:19 AM, Stefan Majewsky <stefan.majew...@googlemail.com> wrote: > Hi, > > I'm currently working on the libkdegames build system. For a major > cleanup, libkdegames is breaking source and binary compatibility in > the 4.9 release. I figured this is the right time to move away from a > self-installed find-script to a ProjectConfig.cmake file. > > Now I'm wondering about the version numbers. The 4.8 release had: > > set_target_properties(kdegames PROPERTIES VERSION 5.1.0 SOVERSION 5) > > When I broke compatibility, I had bumped this to 6.0.0 and 6, respectively. > > My problem is the following: I understand that installing a > KDEGamesConfigVersion.cmake file should allow third-party projects to > write something like this into their CMakeLists.txt: > > find_package(KDEGames 4.9.0 REQUIRED) > > But I think they need to write "6.0.0", since that's the version of > the library. But I want to have the KDE release number in there. Can > one solve this problem? > > Greetings > Stefan > > P.S. Please answer on kde-devel@, the CC is just to get attention from > the right people. > >>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << You misunderstood the SOVERSION and the your version. SOVERSION is to track ABI[1] version and library version is to track API version. They are different things.
For example, libkdecore is now 5.8.0, but still the api is 4.7. ABI compatibility mean no need to recompile, API compatibility means no need to change the code. [1] http://en.wikipedia.org/wiki/Application_binary_interface >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
