Re: shared lib requires main ?!

[salsaman]

Hi again Ralph !

Following your advice and using the -module flag has indeed removed the leading "lib" from the real library as required.

However, in the installation directory I now see (for example):

foo.a foo.la foo.so

First of all I only want the "foo.so" to be installed.

Second, I need to change the file extension in the install directory. In one directory, there should be no file extension (if possible), so "foo.so" is installed as just "foo". In a second directory (with a different Makefile.am) again only "bar.so" should be installed, however the file extension should be ".wo" so it ends up as "bar.wo"

Of course, this needs to be done in a portable way.

Is this possible with automake and libtool, or would a post-install script which deletes and renames be necessary ?

Regards again,
Gabriel.
http://lives.sourceforge.net

On Sun, Nov 2, 2008 at 12:50 PM, Ralf Wildenhues <address@hidden> wrote:

Hello Gabriel,

please keep the list in Cc:, thanks.

* salsaman wrote on Sun, Nov 02, 2008 at 04:20:18PM CET:

> This is off-topic for the bug, but please can you give me one more tip if
> possible; the local libraries are created as e.g.
> libfoo.la
>
> Depending on the particular build directory, I would like the real libs to
> be just:
> foo
>
> or
>
> foo.wo
>
> Using automake, do you know if this is possible ?

With libraries named libfoo.la, there will be a libfoo.so after
installation.  If you want to avoid the 'lib' prefix: that is only
portable for modules, but not for libraries (and libtool strongly
encourages portable naming).  Modules are denoted with the -module
link flag, so you'd use something like
 pkglib_LTLIBRARIES = foo.la
 foo_la_LDFLAGS = -module

and most often, -avoid-version is used for modules, too.

Hope that helps.

Cheers,
Ralf