>>I'd like your help to name the OpenSSL libraries. The idea I have >>right now is the following (base names are 'osslc' for 'libcrypto', >>'ossls' for 'libssl', and one adds 's' for single-threaded or 'm' for >>multithreaded, as well as 'd' when it's a debug build):
In keeping with Windows tradition, I would move that you NOT use the letter 's' for single-threaded, but rather use the "mt" designation for "multi-threaded" or "mtd" for "multi-threaded-debug" would be my preference. No "mt" designation within the library name would imply single-threaded. It's either multi-threaded or it's not. For example, the use of "osslcmtd.lib" immediately implies using the crypto multi-threaded-debug-static import library. With regards to libeay or ssleay shared libraries, I believe you can leave them as is for now. Due to the possibility of binary incompatibilities, one cannot hope to successfully integrate someone else's build with 100% certainty. It also forces the developer to think about the ramifications when using the shared DLL's on an end-users machine, especially when multiple products each use "their" version of those filenames. We can always rename it to whatever we want to avoid those issues anyways. So you shouldn't need to build in some convoluted naming scheme... Rob ***************************************************************** DISCLAIMER: The information contained in this e-mail may be confidential and is intended solely for the use of the named addressee. Access, copying or re-use of the e-mail or any information contained therein by any other person is not authorized. If you are not the intended recipient please notify us immediately by returning the e-mail to the originator. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
