But there is another problem which Unix-style Configure doesn't solve
now:
dll can include VERSION_INFO resource. Now Configure creates .rc file
only if IsMK1MF is set. I think that if we want to have native Win32
dll, we should include this resource, even if build environment is
completely Unix-style.
Care to figure out and tell how to do it with windres and ld? I mean
I've never done this... This one probably doesn't have to be mingw
specific, cygwin people [Corinna?] might appreciate it just as much.
Here is preliminary patch to generate resource sections for DLLs.
I've chosen a bit different approach, see and check the latest snapshot.
In addition to this resource thing the snapshot engages applink. The
latter makes it possible to use .DLLs compiled with newer MSC [tested
with cl version 13, a.k.a. 2003] used with mingw-compiled application
and vice versa. At the very least test suits pass with replacement .DLLs:-)
I call it preliminary, because:
1. DLL name issue is not permanentely settled. MSVC build creates
libeay32.dll and ssleay32.dll, and Mingw build crypto32.dll and
ssl32.dll. Patch includes code to support this difference, but I'm
not absolutely sure it belongs there.
So we have to decide on unified naming convention for both MSC and
mingw. Suggestion is to embed version number into name, but remaining
questions are:
- do we still stick to 8.3 naming?
- do we want to denote dll origin in its name?
Last question means that crypto099 doesn't really give you a hint that
it's an OpenSSL library. A.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [EMAIL PROTECTED]
