Re: lib*.so symlink

[Alexandre Oliva]

On Feb  4, 2001, Brian May <address@hidden> wrote:

> So the obvious solution is to move libx.la (and possible libx.so) into
> libx1 and libx2, but that means libx1 and libx2 both conflict and
> cannot be installed at the same time :-(

If libx is a module, that's unfortunately true: you really can't have
them both installed at the same time.  You can only have one .la file
at a time, and that's all lt_dlopen will look for.  It doesn't support
versioning.  Maybe it should?  `lt_versioned_dlopen (libname, current,
revision, age)' sounds like a good addition to libltdl.  Then, it
would make a lot of sense to install versioned copies of libx.la
modules.  The down side is that we'd have to duplicate the versioning
code in libltdl :-(  But this looks promising to me.  Any takers?

If it's a library, you only need the .la for development, and you can
only be developing for one version at a time, so it's ok to have the
.la file in the dev package.

> i) what linking libx.la, the version pointer to by libx.so is used?

s/what/when/, yes.

> ii) when dlopening libx.la, the version pointed to by libx.so is used?

Nope, the version pointed to by the dlname encoded in libx.la, that
happens to be libx.so.MAJOR.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  address@hidden, redhat.com}
CS PhD student at IC-Unicamp        address@hidden, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me