[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

crosscompiled .exe (Re: crosscompiling dll linux->mingw32)

From: Guido Draheim
Subject: crosscompiled .exe (Re: crosscompiling dll linux->mingw32)
Date: Thu, 26 Apr 2001 20:21:35 +0200

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-line gets really 
called with a "-o pfe.exe" for program pfe, the libtool will create
builddir/pfe and builddir/.libs/pfe.exe. Does the native-build
libtool do sth. different here? I don't have a win32-environment
here at the moment, but I think not (but how do people make
dependent rules on these platforms?).

/bin/sh ./libtool --mode=link i386-mingw32msvc-gcc  -D_export=__dllexport -Wall 
 -W,-E -W,--warn-common -o pfe.exe
-export-dynamic main-stdc.o -lkernel32  -L.libs -lpfe 
generating import library for `libpfe-0-30-97.dll'
i386-mingw32msvc-dlltool --as=i386-mingw32msvc-as --dllname libpfe-0-30-97.dll 
--def .libs/libpfe-0-30-97.dll-def --output-lib
i386-mingw32msvc-gcc -D_export=__dllexport -Wall -W,-E -W,--warn-common -o 
.libs/pfe.exe main-stdc.o -Wl,--export-dynamic 
-lkernel32 -L/usr/src/cvs/pfe-30/Release/i386-mingw32msvc/.libs 
.libs/libimp-pfe-0-30-97.a -Wl,--rpath -Wl,/programs/pfe
creating pfe.exe

Any argument why that is how it is?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]