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
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
Remove the 'shared' from your Configure line.
On 7/27/06, Du Jingwu <[EMAIL PROTECTED]> wrote:
Hi all, I'd like to use openssl in embedded system. I learn from the following
url that openssl can be trimmed down to 200K.
http://groups.google.com/group/mailing.openssl.users/browse_frm/thread/9a52
