Hi Roumen,
> Define NOCRYPT or try to define WIN32_LEAN_AND_MEAN for mingw-w64.sf.net
> project 32 bit version.
> I think that is good WIN32_LEAN_AND_MEAN to be defined for mingw. I
> confirm that openssl cross-compiles well with headers from mingw.org
> project .
>
Thanks for your hint - it was definitely the right direction. After
couple of tries it turned out that for 32-bit compiler provided by
mingw-w64.sf.net project it will be necessary to add a new config into
./Configure script.
Here is my proposal that works fine for me:
"mingw64_32", "gcc:-mno-cygwin -DL_ENDIAN -O3 -Wall
-DWIN32_LEAN_AND_MEAN -DUNICODE -D_UNICODE:::MINGW32:-lws2_32 -lgdi32
-lcrypt32:THIRTY_TWO_BIT RC4_CHUNK_LL DES_INT
EXPORT_VAR_AS_FN:${x86_asm}:coff:win32:cygwin-shared:-D_WINDLL:-mno-cygwin:.dll.a",
So in the end we will have the following configs:
- mingw (32-bit compiler by mingw.org)
- mingw64 (64-bit compiler by mingw-w64.sf.net)
- mingw64_32 (32-bit compiler by mingw-w64.sf.net)
I you (or the relevant maintainer) find it sane I would appreciate to
see it in the next 1.0.0beta. I am ready to volunteer for a
documentation patch saying some info about mingw64_32 target.
FYI - for a successful build you need 32-bit mingw-w64 toolchain with
the libcrypt32.a fix described here:
https://sourceforge.net/tracker/?func=detail&atid=983354&aid=2905470&group_id=202880
--
kmx
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
