Thanks for your reply, Jeremy. Yes, I'd like to have https client, scp & sips client to use the openssl library. So the dynamic linking should be a better choice.
And thanks for Richard Davis to point out the error in my original post: The 200k bytes is just a saving of turnning some cipers off, not the total library size. And he gave me some configure options and hints. Thank you all for your warm help! Best regards, Levin Du On Friday 28 July 2006 13:38??Jeremy Farrell wrote?? > Are you really intending to have the library as a shared object in this > embedded system? How many different executables will be linked against > it? > > A more usual approach if you want to minimize size is to do a static > build of the OpenSSL library and link against that. Your executable will > then only include the bits of OpenSSL code that it needs. You're only > likely to get space benefit from using a shared library if many > different executables are linked against OpenSSL and running at the same > time. In this case it might be possible to slim down the shared object > to contain just what you need, but I don't think there's an easy way to > do so. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
