Point taken - I realise this stuff is time consuming. On the other
hand, we only have to address it once, and then come up with a set of
rules for the project.
The link I provided suggests some rules for using -version-info:
http://www.gnu.org/software/libtool/manual.html#Versioning
Ther
I'm sure that there are a lot of things that we do wrong in the
configure scripts, but so far I can't find anyone who really know what
the right thing to do with the autotools is. It would be nice if there
was a "Best Practices" document for the autotools that we could refer to.
I personally
I've just been looking at the way libtool is used by ActiveMQ-CPP,
in anticipation of creating some Debian packages.
The parameters to -version-info are defined like this:
current = 2 = current interface version
revision = 1 = the revision of the library (binary compatibility is
preserved acro
