From: Dr S N Henson <[EMAIL PROTECTED]>
drh> An external DLL might use DECLARE_ASN1_FUNCTIONS() in its header file
drh> and then drag in OPENSSL_EXTERN if it was added to the macro.
drh> OPENSSL_EXTERN would then need that behaviour to work.
drh>
drh> If OPENSSL_EXTERN is considered illegal in external applications they
drh> need some other way to achieve the same end.
So one needs to make sure OPENSSL_BUILD_SHLIB is only defined when
appropriate, no? But I do understand the concern if for example the
SSL library would need to make global symbols and at the same time
reach global symbols from the crypto library...
What I mean was that it wold be stupid for external applications and
DLL's to OPENSSL_EXTERN as if OPENSSL_BUILD_SHLIB was defined...
--
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]
