I was able to compile openssl executable for Win32 on my Linux machine (just
like I do for my stunnel for a long time).
The target definition in Configure file was:
"mingw32msvc",
"i386-mingw32msvc-gcc:-DL_ENDIAN -fomit-frame-pointer -O3 -m486 -Wall:::-lws
ock32 -lgdi32:BN_LLONG ${x86_gcc_des}
${x86_gcc_opts}::::::::::win32::::i386-mingw32msvc-ranlib",
My cross-compiler was mingw32-linux-x86-glibc-2.1.tar.gz. I had to rename
"openssl" to "openssl.exe"
Then I created dlls:
perl util/mkdef.pl 32 libeay > ms/libeay32.def
perl util/mkdef.pl 32 ssleay > ms/ssleay32.def
i386-mingw32msvc-dllwrap --dllname libeay32.dll --output-lib
libeay32.a --def ms/libeay32.def libcrypto.a -lwsock32 -lgdi32
i386-mingw32msvc-dllwrap --dllname libssl32.dll --output-lib
libssl32.a --def ms/ssleay32.def libssl.a libeay32.a
My questions:
1. What is the reason behind
#ifdef WINDOWS #include "bss_file.c"
at apps/apps.c and other places?
(after Vadim Fedukovich <[EMAIL PROTECTED]> on Mon, 17 Dec 2001 18:04:06 +0200)
2. Is there a chance for the cross-compilation to be supported? Should I
send someone a patch?
You can download results of my work from from
ftp://ftp.mirt.net/openssl/binary/.
BTW: Am I the on the only developer that doesn't have a Windows development
machine?
Best regards,
Mike
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
