The following is the beginning of my Makefile.am script:
include_HEADERS = project.h
lib_LTLIBRARIES = libproject.la
noinst_HEADERS = proj_list.h
libproject_la_LDFLAGS = -version-info 2:0:1
which worked fine when with previous loading of a library with 2:0:0
versioning code.
But now, when I
On Sunday 2009-05-03 17:41, Gerald I. Evenden wrote:
>libproject_la_LDFLAGS = -version-info 2:0:1
>
>which worked fine when with previous loading of a library with 2:0:0
>versioning code.
>
>But now, when I go through the autoreconf, configure, compile and install I
>get:
>
>libproject.so.1.1.0
Hi Gerald,
On 5/3/2009 9:51 AM, Jan Engelhardt wrote:
On Sunday 2009-05-03 17:41, Gerald I. Evenden wrote:
libproject_la_LDFLAGS = -version-info 2:0:1
which worked fine when with previous loading of a library with 2:0:0
versioning code.
But now, when I go through the autoreconf, configur
On Sunday 2009-05-03 18:58, John Calcote wrote:
>
>It appears that Libtool is smart enough to detect ridiculous cases, but it
>should probably throw an error of some sort, rather than simply generate
>code with a different version number.
Since libtool is "just" a linker as far as is considered h
On Sunday 03 May 2009 1:02:54 pm Jan Engelhardt wrote:
> On Sunday 2009-05-03 18:58, John Calcote wrote:
> >It appears that Libtool is smart enough to detect ridiculous cases, but it
> >should probably throw an error of some sort, rather than simply generate
> >code with a different version number.
On Sunday 2009-05-03 20:40, Gerald I. Evenden wrote:
>
>What I did to the library was add several procedures
That in itself would cause a bump in the 'current' number to 3.
>but the original
>functions were not changed nor affected.
So 'age' becomes 1, since you are still supporting (3-1) = 2.
In a shared library there are about 8 routines out over 100 that refer to
libgsl and libpthread. A frequent situation may arise where an application
program has no need for using the 8 procedures infected with other library
needs.
At the current time, when I try to link such a program I get a
On Sunday 2009-05-03 23:32, Gerald I. Evenden wrote:
>In a shared library there are about 8 routines out over 100 that refer to
>libgsl and libpthread. A frequent situation may arise where an application
>program has no need for using the 8 procedures infected with other library
>needs.
>
>At
Jan Engelhardt writes:
> On Sunday 2009-05-03 23:32, Gerald I. Evenden wrote:
>> In a shared library there are about 8 routines out over 100 that
>> refer to libgsl and libpthread. A frequent situation may arise where
>> an application program has no need for using the 8 procedures
>> infected w
Gerald,
On 5/3/2009 12:40 PM, Gerald I. Evenden wrote:
I want to thank you all for the assistance, however I still find the libtool
manual not very illuminating. In particular, I used section 7.3 in make my
release number and, in particular, item 5 related to adding an interface
since last rele
Gerald,
On 5/3/2009 3:32 PM, Gerald I. Evenden wrote:
In a shared library there are about 8 routines out over 100 that refer to
libgsl and libpthread. A frequent situation may arise where an application
program has no need for using the 8 procedures infected with other library
needs.
At the cu
11 matches
Mail list logo
