On 2006.10.25 at 13:36:11 +0200, Andy Polyakov wrote:
> 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? Really I think that time to forget 8.3 naming is already here for five years or so. I suspect that 32-bit openssl applications won't work on Win16 with Win32s anyway. And it is only case where 8.3 matters for 32bit DLLs. As to source file naming, I don't think 8.3 is neccessary even if DJGPP target is supported. It is easier to use cross-compiler or use Windows platform for compiling. > - 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. This is good reason. eay suffix did exactly so. But I'm not sure that it is strictly neccessary. At least origin is denoted in VERSION_INFO > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > Development Mailing List openssl-dev@openssl.org > Automated List Manager [EMAIL PROTECTED] > ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
