the
other, but not always -- and not by the same increment.
How is major:minor:revision in libraries related to package versions?
Using a scheme that
is easier to understand would hopefully reduce mistakes in library
versioning.
No, it just ensures that the version numbers associated with shared
that
is easier to understand would hopefully reduce mistakes in library
versioning. Naturally this still assumes that no operating system truly
needs a different versioning style.
--
Lasse Collin | IRC: Larhzu @ IRCnet Freenode
___
https://lists.gnu.org
library ABIs with minorver updates...and sometimes
majorver updates don't modify the ABI at all but simply represent a big
new feature addition -- or a promotion to 'stable' (**)
Using a scheme that
is easier to understand would hopefully reduce mistakes in library
versioning.
No, it just
.
There are also long-standing traditions associated with various OSs.
Could you elaborate? Could the traditions explain why on some operating
systems Libtool does library versioning in a way that conflicts with the
operating system documentation?
On Fri, 10 Jun 2011, Lasse Collin wrote:
It's not clear
the library versioning.
The OS is just there to help with the selection process.
Packagers care about library versions too. Incrementing the major
version means that packagers need to recompile everything that depend on
the library. It is annoying if the major version is incremented without
a reason
On 2011-06-14 Bob Friesenhahn wrote:
On Tue, 14 Jun 2011, Lasse Collin wrote:
Please read the section Understanding shared libraries
number rules (it's short):
http://www.openbsd.org/faq/ports/specialtopics.html
If this web page text is correct, then I agree that libtool is doing
On 06/14/2011 11:26 AM, Lasse Collin wrote:
On 2011-06-14 Bob Friesenhahn wrote:
On Tue, 14 Jun 2011, Lasse Collin wrote:
Please read the section Understanding shared libraries
number rules (it's short):
http://www.openbsd.org/faq/ports/specialtopics.html
If this web page text is
On Tue, Jun 14, 2011 at 12:26, Lasse Collin wrote:
On 2011-06-14 Bob Friesenhahn wrote:
On Tue, 14 Jun 2011, Lasse Collin wrote:
Please read the section Understanding shared libraries
number rules (it's short):
http://www.openbsd.org/faq/ports/specialtopics.html
If this web page
, the older library supporting the same current-age may be
deleted once the new library is installed.
The applications are really what care about the library versioning.
The OS is just there to help with the selection process.
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http
I recently made a bug report that Libtool does shared library
versioning wrong on *BSDs:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8765
After that bug report I have got a feeling that Libtool may have
comparable bugs on a few other operating systems too. I'm not sure
that I'm reading
On 2011-06-10 Mike Frysinger wrote:
iirc, what you're expecting is Linux style on systems which dont use
Linux style. so libtool is working correctly as the maintainers of
those respective OS's intended. while you might disagree with their
decisions, it doesnt make the libtool behavior
Thank you for your reply, Ralf
This is not possible, in general. It has nothing much to do with
libtool either, because typically it's just the system semantics that
allow for only one unversioned soname symlink.
OK, but an easy check whether I can safely link with the lib would be nice, too.
be used. However, library versioning is primarily a concept to
allow support of existing binaries. Recompiling is intended to always
work against the newest versions of things.
A corollary is that, when you are building software in order to
distribute it in binary form, then build it against the oldest
Hello,
libtool has a nice way how to version libraries.
However, how do I tell to the linker that my app has to link with the
library that supports interface x?
This seems as a very trivial question, but I haven't found the answer in
the manual, is that possible?
Regards,
Matej
Hello Matěj,
* Matěj Týč wrote on Mon, Feb 02, 2009 at 09:37:20PM CET:
libtool has a nice way how to version libraries.
However, how do I tell to the linker that my app has to link with the
library that supports interface x?
This is not possible, in general. It has nothing much to do with
Hi Lucien,
On 30 Mar 2007, at 16:59, Lucien GENTIS wrote:
Gary V. Vaughan a écrit :
On 29 Mar 2007, at 15:48, Lucien GENTIS wrote:
Gary V. Vaughan a écrit :
On 26 Mar 2007, at 12:47, [EMAIL PROTECTED] wrote:
Quoting Gary V. Vaughan [EMAIL PROTECTED]:
On 25 Mar 2007, at 16:50, Lucien GENTIS
Hi Lucien,
On 29 Mar 2007, at 15:48, Lucien GENTIS wrote:
Gary V. Vaughan a écrit :
On 26 Mar 2007, at 12:47, [EMAIL PROTECTED] wrote:
Quoting Gary V. Vaughan [EMAIL PROTECTED]:
On 25 Mar 2007, at 16:50, Lucien GENTIS wrote:
That means:
CURRENT is replaced by CURRENT - AGE (69 - 38 =
Gary V. Vaughan a écrit :
Hi Lucien,
On 29 Mar 2007, at 15:48, Lucien GENTIS wrote:
Gary V. Vaughan a écrit :
On 26 Mar 2007, at 12:47, [EMAIL PROTECTED] wrote:
Quoting Gary V. Vaughan [EMAIL PROTECTED]:
On 25 Mar 2007, at 16:50, Lucien GENTIS wrote:
That means:
CURRENT is replaced by
Hi to all,
I would like to use libtool to manage versioning of a library called,
say mylib
libtool version is 1.5.6-6 under Linux Debian Sarge 3.1 stable
In the configure.ac at the project root, I have the lines:
mylib_CUR=69
mylib_REV=47
mylib_AGE=38
AC_SUBST(mylib_CUR)
AC_SUBST(mylib_REV)
Hi Lucien,
On 25 Mar 2007, at 16:50, Lucien GENTIS wrote:
That means:
CURRENT is replaced by CURRENT - AGE (69 - 38 = 31)
REVISION is replaced by AGE
AGE is replaced by REVISION
http://www.gnu.org/software/libtool/manual.html#Libtool-versioning
Cheers,
Gary
--
())_.
20 matches
Mail list logo
