From: Dr S N Henson <[EMAIL PROTECTED]>
drh> > definitions for the Win32 case. Of course, what you say above means
drh> > that OPENSSL_EXTERN will have different values depending on if you're
drh> > building the DLL or using it. That's pretty easy to do if we use a
drh> > macro BUILD_SHLIB as a flag. Of course, if any other DLL needs to
drh> > reexport OpenSSL symbols (is that what you meant?), it wll have to
drh> > defined BUILD_SHLIB as well...
drh> >
drh>
drh> Well the issue with additional DLLs is that they may need to import some
drh> variables defined in OpenSSL and export some of their own which the new
drh> ASN1 macros create. So the stuff in the OpenSSL headers needs to be the
drh> import declaration whereas stuff in the additional DLLs headers needs to
drh> be the export declaration when the DLL is being built.
Ah, that makes things simpler. But it would probably be smart to use
the name OPENSSL_BUILD_SHLIB instead of just BUILD_SHLIB :-).
--
Richard Levitte \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
Redakteur@Stacken \ SWEDEN \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, Celo Communications: http://www.celocom.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]
