On Sun, Dec 07, 2014 at 10:01:17AM +0800, David Maciejak wrote: > I agree with you Rodolfo that it should be better to increase the minor > version number instead. This is not just "numbers after .so.". And was a bit wrong, AGE should also be increased.
From info libtool:
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'.
If two libraries have identical CURRENT and AGE numbers, then the
dynamic linker chooses the library with the greater REVISION number.
If you want to use libtool's versioning system, then you must specify
the version information to libtool using the `-version-info' flag
during link mode (*note Link mode::).
This flag accepts an argument of the form
`CURRENT[:REVISION[:AGE]]'. So, passing `-version-info 3:12:1' sets
CURRENT to 3, REVISION to 12, and AGE to 1.
If either REVISION or AGE are omitted, they default to 0. Also note
that AGE must be less than or equal to the CURRENT interface number.
Here are a set of rules to help you update your library version
information:
1. Start with version information of `0:0:0' for each libtool library.
2. Update the version information only immediately before a public
release of your software. More frequent updates are unnecessary,
and only guarantee that the current interface number gets larger
faster.
3. If the library source code has changed at all since the last
update, then increment REVISION (`C:R:A' becomes `C:r+1:A').
4. If any interfaces have been added, removed, or changed since the
last update, increment CURRENT, and set REVISION to 0.
5. If any interfaces have been added since the last public release,
then increment AGE.
6. If any interfaces have been removed or changed since the last
public release, then set AGE to 0.
*_Never_* try to set the interface numbers so that they correspond
to the release number of your package. This is an abuse that only
fosters misunderstanding of the purpose of library versions. Instead,
use the `-release' flag (*note Release numbers::), but be warned that
every release of your package will not be binary compatible with any
other release.
--
Regards, --
Sir Raorn. --- https://plus.google.com/+AlexeyFroloff
pgpSl1xtrjoYe.pgp
Description: PGP signature
