Richard, Thanks for the response. I'm aware of the potential configuration issues. If I were to do as you suggest and simply use libcrypto (the thought had occurred to me already), then how can I integrate the building of libcrypto into my company's build process (it's actually quite complex)? I suppose that I could have our build simply run the openssl config script and then rebuild the lib for each platform. Are you aware of an approach that would allow me to only configure and build libcrypto and not the entire openssl distribution?
Thanks, Doug -----Original Message----- From: Richard Levitte - VMS Whacker [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 13, 2004 1:13 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Question about #defines In message <[EMAIL PROTECTED]> on Mon, 12 Jan 2004 10:45:49 -0700, "Doug Smith" <[EMAIL PROTECTED]> said: doug> Is there any documentation on what some of the #defines in the source do? doug> For example, what are these for: doug> doug> doug> doug> OPENSSL_NO_SHA doug> doug> OPENSSL_NO_ENGINE doug> doug> doug> doug> I'm trying to take the RSA code and use it as a standalone doug> library, but I'm not entirely certain about which options to use doug> for compilation. The OPENSSL_NO_* macros are there to turn off the corresponding algorithms. So OPENSSL_NO_SHA turns off all SHA algorithms, and so on. As for breaking out a specific algorithm from OpenSSL, I wouldn't recommend it. I know, back in SSLeay days, this was explicitely supported (because EAY started off with separate libraries that became part of SSLeay later). However, this may lead to configuration differences that can be disastrous if the broken out code would be combined with OpenSSL (say that some type is defined as long in OpenSSL but defined as int in the broken out code. On 64-bit architectures, int and long are sometimes of different sizes. You can probably deduce what happens ...). Can't you simply link with libcrypto.a? What happens is that only the object files that you really need are pulled out, so it wouldn't make much difference for you binary... ----- Please consider sponsoring my work on free software. See http://www.free.lp.se/sponsoring.html for details. You don't have to be rich, a $10 donation is appreciated! -- Richard Levitte \ Tunnlandsv�gen 3 \ [EMAIL PROTECTED] [EMAIL PROTECTED] \ S-168 36 BROMMA \ T: +46-8-26 52 47 \ SWEDEN \ or +46-708-26 53 44 Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED] Member of the OpenSSL development team: http://www.openssl.org/ 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 User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
