Re: Possible library versioning approach -- (evaluation requested)
> > If you are using libtool and automake, it would be:
> > LDFLAGS = ..... -release @OTHERLIB_NAMES@
> Doesn't -release actually change the library name, not the soname?
It doesn't change the library name, no, look at libbfd as an example.
> If you weren't using libtool I
> presume setting an arbitrary soname would usually be trivial, but
> unfortunately with libtool, I'm not sure it's possible, or that the
> maintainers would have any interest in making it possible.
You may not have yet read the Library packaging manual further enough, but
with " -release somethinglib -soname 0:0:0" you should get the following:
liblibrary-somethinglib.so.0.0.0 (actual library file)
liblibrary-somethinglib.so.0 (the symlink matching the soname)
liblibrary.so (the symlink used for library linkage time)
and as a real-life example, something like this :
lrwxrwxrwx 1 dancer dancer 33 2002-12-15 00:33 libdmsocket-0.32.4.cvs.5.so.0 -> libdmsocket-0.32.4.cvs.5.so.0.0.0
-rwxr-xr-x 1 dancer dancer 36607 2002-12-15 00:33 libdmsocket-0.32.4.cvs.5.so.0.0.0
-rw-r--r-- 1 dancer dancer 32310 2002-12-15 00:33 libdmsocket.a
-rwxr-xr-x 1 dancer dancer 880 2002-12-15 00:33 libdmsocket.la
lrwxrwxrwx 1 dancer dancer 33 2002-12-15 00:33 libdmsocket.so -> libdmsocket-0.32.4.cvs
> > OTHERLIB_NAMES=whatever6-whateverelse3-whateverelse2
> > However, I don't know of a way to reliably check sonames in
> > configure scripts...
> I'd wondered about that too, but in many cases, for example for glib
> and guile, it's easy to figure it out via glib-config and guile-config
That is nice.