Customizing soname

Hello, I had an issue that I solved in patching libtool, I am not sure this was the right thing to do, but if it was, I think it should go into libtool. I require to produce a shared library that whose name is customizable by the user. I use autoconf/automake/libtool in order to build the syste

Re: Customizing soname

Alon Bar-Lev wrote: > Hello, > > I had an issue that I solved in patching libtool, I am not sure this was > the right thing to do, but if it was, I think it should go into libtool. > > I require to produce a shared library that whose name is customizable by > the user. Why? I can understand want

Re: Customizing soname

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

Re: Customizing soname

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

Re: Customizing soname

On 3/27/08, Peter O'Gorman <[EMAIL PROTECTED]> wrote: > 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@ > $(LI

Re: MinGW linux to win32 cross compiler and the test suite

Erik de Castro Lopo wrote: Hi all, I have the beginnings of a solution to this issue. If I hack the libtool generated wrapper script and replace this: exec "$progdir/$program" ${1+"$@"} with WINEDLLPATH="$PATH;$WINEDLLPATH" exec wine "$progdir/$program" ${1+"$@"} My test

Re: Customizing soname

* Alon Bar-Lev wrote on Thu, Mar 27, 2008 at 06:35:48PM CET: > 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? > Because I generate a plu

Re: Customizing soname

On 3/28/08, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > Is the set of possible names limited? If yes, please read > > Hi, No... Sorry... I need to produce a different name chosen by configure and/or user

Re: Customizing soname

Alon Bar-Lev wrote: > On 3/28/08, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: >> Is the set of possible names limited? If yes, please read >> >> > > Hi, > No... Sorry... I need to produce a different name