>>>>> On Mon, 23 Oct 2006 16:09:03 +0200, Andy Polyakov said: > > >>> 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. > >> BTW, what is the meaning of "32" in the names? > > > > Theoretically there can be 16-bit versions of the DLLS for Win16. > > In future, when Mingw builds would support x86_64 architecture, there > > sould be 64-bit versions. (Now, I suppose only MSVC builds can generate > > 64-bit dlls) > > While this might apply to mixture of 16- and 32-bit ["might" means that > I've never actually seen it myself and therefore can't actually tell], > on Win64 even 64-bit DLLs are customarily called *32.dll. And I refer to > system DLLs, not those we build! I suppose MS has chosen to keep 32 in > name in order to simplify life for developers, so that they can keep > link command lines in their projects and can be excused from tweaking > arguments to LoadLibrary calls in Win64 port. I'd say 32 in name is more > of less meaningless artifact. At least it's more than sufficient to > maintain *any* consistent naming between 32- and 64-bit builds.
Right, there are already unofficial 64-bit OpenSSL DLLs available with 32 in their name...but dropping it at the same time as "eay" sounds like a good option to me. -- Martin Simmons LispWorks Ltd http://www.lispworks.com/ ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
