On 2012-05-02, Stefan Majewsky <stefan.majew...@googlemail.com> wrote: > On Wed, May 2, 2012 at 8:30 PM, Weng Xuetian <wen...@gmail.com> wrote: >> For example, libkdecore is now 5.8.0, but still the api is 4.7. > > When the VERSION was 5.1.0 previously, can I go back to 4.9.0 to reach > consistency with the KDE release, while I still bump the SOVERSION > from 5 to 6?
both the VERSION and SOVERSION in the cmake line relates to the same thing. and is completely unrelated to api versioning. technically, cmake might be able to do that, but oh boy, it would be weird. for example, I have on my file system: /usr/lib/libkio.so /usr/lib/libkio.so.5 /usr/lib/libkio.so.5.7.0 one being symlink to two being symlink to three being the real file. the loader basicalyl looks at applications for the NEEDED entries: objdump -x /usr/bin/kioclient | grep NEEDED | grep kio NEEDED libkio.so.5 then it looks in RPATH, $LD_LIBRARY_PATH, ld.so.conf paths and the build in paths in ld for a file named like that and loads that. so, if libkio.so.5 pointed to libkio.so.4.9, I guess things would actualy still work, but you would confuse the hell out of everyone. and going backwards - then you risk actually colliding with earlier libkdegames editions on the sytem /Sune >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
