Hi, libtool is tricky but has a clear pattern there. Starting with a c:r:a of 5:1:4 set the revision to 0 and increase the current to 6 to account for the ABI change. Since the original API is still supported (compatible changes only) increase the age to 5 (this indicates all prior APIs are supported). See e.g. http://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html
So it's 6:0:0 if you broke the API, and for ABI changes only it's 6:0:5 actually. Am 10.02.2009 um 23:41 schrieb Hendrik Sattler: > Am Dienstag 10 Februar 2009 21:43:10 schrieb Alex Kanavin: >> 2009/2/10 Alex Kanavin <a...@sensi.org>: >>> Er, I thought that Marcel would do the API version update - anyway, >>> just to be sure, how should it look like? >> >> Nevermind, figured it out (hopefully). Here's the updated patch set >> for >> review. > > No, 6:0:0 is not the right thing but the -version-info libtool thing > is just > insane. > It sets the soname to libopenobex.so.6 but we want libopenobex.so.2. regards, Christian ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Openobex-users mailing list Openobex-users@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/openobex-users
