Alon Bar-Lev wrote:
> On 3/27/08, Peter O'Gorman <[EMAIL PROTECTED]> wrote:
>> Why? I can understand wanting to change the extension, we have -shrext
>> for that. But why do you want the user to have the option to set the name?
>
> Hi!
>
> Because I generate a plugin, each configuration results in different plugin.
> I also have this when I produce proxy shared library.
>
> I can do this very simple with automake/libtool if I rename the output. But
> not got any solution of how to correct the soname.
>
> Maybe I can do this with some ELF hacking utility, but I think that adding
> the ability to override the soname via libtool is the simplest and cleanest.
Does automake complain if you do something like:
@PLUGIN_TARGET@: foo.lo
$(LIBTOOL) --mode=link --tag=CC $(CCLD) -o @PLUGIN_TARGET@ \
foo.lo -avoid-version -module
install-exec-hook: @PLUGIN_TARGET@
$(LIBTOOL) --mode=install $(INSTALL) @PLUTIN_TARGET@ \
$(DESTDIR)$(libdir)
?
Peter
--
Peter O'Gorman
http://pogma.com
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
