4 Sep
2014
4 Sep
'14
11:35 a.m.
On Wed, Sep 03, 2014 at 06:57:50PM +0300, Vasil Velichkov wrote:
Hi Holger, Ciaby,
On 3.09.2014 16:25, Holger Hans Peter Freyther wrote:
Right.
A new library version that still supports the previous interfaces
needs to bump current and age, if the base is 6:0:0, then the update
needs to be 7:0:1.
If you remove interfaces you don't want anymore, ie. you break
backward compatibility, you have to reset age and bump current, ie.
7:0:0
On Wed, Sep 03, 2014 at 04:21:13AM -0500, Ciaby
wrote:
It is normal that 6:0:1 gives a so with major version 5, because
6:0:1 means that the library supports interfaces 5 and 6
See http://www.gnu.org/software/libtool/manual/html_node/Libtool-versioning.html
So, libtool library versions are described by three integers:
current
The most recent interface number that this library implements.
revision
The implementation number of the current interface.
age
The difference between the newest and oldest interfaces that
this library implements.
In other words, the library implements all the interface
numbers in the range from number current - age to current. I know, it doesn't make sense... but
that's what I got out of building
it with 6.0.1 as version. 6.0.0 works fine. Can you reproduce it?
yes, it is odd.
6:0:1 gives me a so where the major version is 5
something :)
There seems to be a similar issue with the libosmocore library as
well. Did you see the warning generated by lintian?