Well, to borrow from another of your posts earlier on, we would have library names like:
1) osslcm.lib, osslsm.lib: multithreaded SL release builds. 2) osslcm.dll, osslsm.dll: mutlithreaded DLL release builds. The targets under item 2) above would also produce osslcm.lib and osslsm.lib as import libraries (linker stubs?) for the DLLs in question, for targets that link directly to them instead of using LoadLibrary(), meaning we would end up with two pairs of identically named files -- linked to different versions of the CRT. Maybe this isn't much of an issue, I don't know. I'm not sure how one should tell them apart either, if necessary. Perhaps by appending an 's' to the static library builds, much like a 'd' would be to the debug builds? Richard Levitte - VMS Whacker wrote: > > From: Oscar Jacobsson <[EMAIL PROTECTED]> > > oscar> Might I also request some kind of additional identifier that would help > oscar> differing between actual static libraries and dll import libraries? I'm > oscar> not too fussy about how to actually name the stuff, as long as a > oscar> makefile could tell them apart. > > You may, if you tell me what kind of identifier you're after, and what > the purpose would be. > > -- > Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED] > Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47 > \ SWEDEN \ or +46-733-72 88 11 > Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED] > Member of the OpenSSL development team: http://www.openssl.org/ > Software Engineer, GemPlus: http://www.gemplus.com/ > > Unsolicited commercial email is subject to an archival fee of $400. > See <http://www.stacken.kth.se/~levitte/mail/> for more info. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
