Andy Polyakov wrote:
1. Using mingw32 compiler (from http://www.mingw.org)
2. Using cygwin compiler with -mno-cygwin switch to create executables
which do not depend on cygwin.dll
3. Using cross-compiler on some Unix system. I've used cross-compiler
included in Debian GNU/Linux ver./g 3.1 (sarge) as package mingw32
The roadmap is to scrap #1 and make #2 work on both cygwin and msys.
In addition #2 should/will generate .def files and use them when
linking .dll. Idea is to be able to generate drop-in replacement
.dlls for those compiled with MSVC.
This has "just worked" for me for quite a long time now.
??? .dlls generated by our "MSVC" procedure export entry points by
ordinals, while .dlls generated by cygwin/msys - by names. Therefore
it's not drop-in replacement. A.
Disregard that comment, I was lost. I don't interchange MSVC / gcc dll's
on the fly. I was just thinking about the import libraries; a
gcc-compiled DLL will work with an MSVC app if it's linked with the
gcc-specific import library, and vice-versa.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc
OpenLDAP Core Team http://www.openldap.org/project/
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
