Re: libtool versioning

2010-05-03 Thread Jef Driesen
On 02/05/10 03:33, Bob Friesenhahn wrote: On Sun, 2 May 2010, Jef Driesen wrote: I'm trying to understand the libtool current:revision:age versioning scheme. I think I understand how it works, but I noticed that filename of the shared library seems to get different numbers (current-age.age.revi

Re: libtool versioning

2010-05-03 Thread Matěj Týč
>> I'm trying to understand the libtool current:revision:age versioning >> scheme. I think I understand how it works, but I noticed that filename of >> the shared library seems to get different numbers >> (current-age.age.revision). Is that expected? > > The filename generation is dependent on the

Re: libtool versioning

2010-05-03 Thread Bob Friesenhahn
On Mon, 3 May 2010, Jef Driesen wrote: # 6. If any interfaces have been removed since the last public release, # then set age to 0. Shouldn't step #6 included "changed" as well as "removed"? If you change the interface (for example modifying function parameters), backwards compatibility

Re: libtool versioning

2010-05-03 Thread Bob Friesenhahn
On Mon, 3 May 2010, Matěj Týč wrote: If I have understood correctly, the whole LTversion stuff has only one purpose - to inform users what have they installed. More specifically, it provides libtool with the information needed to produce a suitably numbered library to satisfy a purpose

Re: libtool versioning

2010-05-03 Thread Gary V. Vaughan
On 3 May 2010, at 23:09, Bob Friesenhahn wrote: > On Mon, 3 May 2010, Matěj Týč wrote: >>> >> >> If I have understood correctly, the whole LTversion stuff has only one >> purpose - to inform users what have they installed. > > More specifically, it provides libtool with the information need

Re: libtool versioning

2010-05-03 Thread Ralf Wildenhues
Hello Jef, * Jef Driesen wrote on Mon, May 03, 2010 at 09:08:14AM CEST: > On 02/05/10 03:33, Bob Friesenhahn wrote: > >On Sun, 2 May 2010, Jef Driesen wrote: > > > >>I'm trying to understand the libtool current:revision:age versioning scheme. > >>I think I understand how it works, but I noticed th

Re: libtool versioning

2010-05-03 Thread Ralf Wildenhues
Hello, * Matěj Týč wrote on Mon, May 03, 2010 at 05:45:26PM CEST: > If I have understood correctly, the whole LTversion stuff has only one > purpose - to inform users what have they installed. Wrong. It provides a fairly portable abstraction of different versioning schemes implemented in differ

Re: libtool versioning

2010-05-03 Thread Jef Driesen
On 03/05/10 20:00, Ralf Wildenhues wrote: Hello Jef, * Jef Driesen wrote on Mon, May 03, 2010 at 09:08:14AM CEST: On 02/05/10 03:33, Bob Friesenhahn wrote: On Sun, 2 May 2010, Jef Driesen wrote: I'm trying to understand the libtool current:revision:age versioning scheme. I think I understand

Re: libtool versioning

2010-05-03 Thread Ralf Wildenhues
* Jef Driesen wrote on Mon, May 03, 2010 at 08:24:09PM CEST: > Yes, I have read the libtool manual, but it doesn't contain much > info about the resulting filename. Most of the info is about the > c:r:a scheme for input, not the output. Yes, because the output file name is a per-system detail that

Re: libtool versioning

2010-05-03 Thread Michel Briand
Jef Driesen - Mon, 03 May 2010 20:24:09 +0200 >On 03/05/10 20:00, Ralf Wildenhues wrote: >> Hello Jef, >> >> * Jef Driesen wrote on Mon, May 03, 2010 at 09:08:14AM CEST: >>> On 02/05/10 03:33, Bob Friesenhahn wrote: On Sun, 2 May 2010, Jef Driesen wrote: >> The git master version of Libtoo