Why do you believe that stunnel represents the most widely used naming? There are widely deployed applications from
IBM (ships as part of the Access IBM service)
Time Warner's Road Runner
The Kermit Project (Kermit 95)
and many others who distribute ssleay32.dll and libeay32.dll. If anything
I would argue that the naming convention needs to be modified to include
the version number so as to prevent conflicts between 0.9.5, 0.9.6, 0.9.7,
and 0.9.8 all of which have incompatible ABIs.
Jeffrey Altman
Martin Germann wrote:
Hi,
I noticed an inconsistency in the windows library names:
When compiling OpenSSL on windows with gcc (MinGW), the resulting ssl library is called 'libssl32.dll'. Using MS Visual C++ (and Borland C++, i suppose), the resulting binary will be called 'ssleay32.dll'.
This may cause a lot of confusion for users compiling OpenSSL on Win32. Therefore, I suggest to modify the targets for Visual C++ and Borland C++ to also build 'libssl32.dll', as this target name seems to be most widely used (e.g. stunnel).
Regards, Martin ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
smime.p7s
Description: S/MIME Cryptographic Signature
