Re: Shared library versions

[Gary V . Vaughan]

On Wed, 21 Feb 2001, Andrew Clausen wrote:
> 
> OK.  This is all very confusing to understand, because rule 3
> clashes with rule 4 (I assume 4 overrides 3), and the rules aren't
> mutually exclusive.  Let's run through an example:
>
> start: (rule 1)
>       libtool=0:0:0,  linux=0.0.0
>
> add an interface: (rule 4, 5)
>       libtool=1:0:1,  linux=0.1.0
>
> remove an interface: (rule 4, 6)
>       libtool=2:0:0,  linux=2.0.0
>
> If I understand all this correctly, it is weird, and it will confuse
> packagers, maintainers and users.

We never said that it was easy!  Don't worry about the version numbers that 
libtool happens to apply to linux shared libs, that is incidental.  Irix has 
a different scheme, and so does windows and so does... etc.

> So, who's going to defend libtool's policy?  *grin*

Okay I'll bite.  Libtool allows you to document your libraries in terms of 
the interface numbers that it supports, and will translate that into an 
appropriate numbering scheme that will provide those semantics on each of the 
architectures that libtool supports.  I wrote a nice explanation of how (and
why) this works in the goat book -- linked from my home page.

Cheers,
        Gary.
-- 
  ___              _   ___   __              _         mailto: address@hidden
 / __|__ _ _ ___ _| | / / | / /_ _ _  _ __ _| |_  __ _ ___       address@hidden
| (_ / _` | '_|// / |/ /| |/ / _` | || / _` | ' \/ _` | _ \
 \___\__,_|_|\_, /|___(_)___/\__,_|\_,_\__, |_||_\__,_|//_/
home page:  /___/                      /___/                  gpg public key:
http://www.oranda.demon.co.uk           http://www.oranda.demon.co.uk/key.asc