On Wed, Mar 06, 2002 at 10:13:55AM +1300, Geoff Thorpe wrote: > > Well yes, but as Richard was explaining - static linking with a libcrypto.a > full of stuff is not that different to linking with a custom-built > "./crypto/des/"-only libdes.a - your linked executable should just contain > the DES bits either way. There's no particular win, that I can see anyway, > to not *building* the rest of libcrypto ... any respectable linker will > only drag in object files from the archive that are required.
True, but I've had people tell me that this isn't as easy as it sounds in particular development environments, such as when building Windows device drivers. Apparently, you have to do a lot of work to convert standard make dependencies to whatever process they use, otherwise you end up recompiling OpenSSL in toto almost every time. I don't know enough about the circumstances (not really caring so much about Windows development). All I know is that it's been something I've had people ask about on several occasions. John ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
