On Apr 28, 2001, "Gary V. Vaughan" <[EMAIL PROTECTED]> wrote:
> libtool would need to build a wrapper program on Windows which would
> call the wrapper script to set the environment up to load the
> correct DLLs and then call the actual program in the .libs
> subdirectory.
I like this idea. It'
"Gary V. Vaughan" wrote:
> > Any argument why that is how it is?
>
> See my last mail.
>
> I can think of two ways around this. Either
> [[...]] or libtool would need to build a wrapper program on Windows
> which would call the wrapper script to set the environment up to load the
> correct DL
On Thursday 26 April 2001 7:21 pm, Guido Draheim wrote:
> Guido Draheim wrote:
> > from that I'd say libtool knows that CC has created a pfe.exe but
> > the automake-rules/vardefs expect a builddir/pfe.exe too. A copy
> > of builddir' pfe to pfe.exe does indeed work. Who's to blame,
> > libtool o
Alexandre Oliva wrote:
>
> On Apr 26, 2001, Guido Draheim <[EMAIL PROTECTED]> wrote:
>
> > Guido Draheim wrote:
> >>
> >> from that I'd say libtool knows that CC has created a pfe.exe but
> >> the automake-rules/vardefs expect a builddir/pfe.exe too. A copy
> >> of builddir' pfe to pfe.exe does
On Apr 26, 2001, Guido Draheim <[EMAIL PROTECTED]> wrote:
> Guido Draheim wrote:
>>
>> from that I'd say libtool knows that CC has created a pfe.exe but
>> the automake-rules/vardefs expect a builddir/pfe.exe too. A copy
>> of builddir' pfe to pfe.exe does indeed work.
Huh? Even though it's a
Guido Draheim wrote:
>
> from that I'd say libtool knows that CC has created a pfe.exe but
> the automake-rules/vardefs expect a builddir/pfe.exe too. A copy
> of builddir' pfe to pfe.exe does indeed work. Who's to blame,
> libtool or automake?
>
It is libtool's fault - even that the final link
