On Fri, 13 Mar 1998, William A. Arbaugh wrote:
> > Eric Young writes:
> > > The other argument is that if one is using DLLs or shared library, who cares
> > > :-).
> > I for one do, because I'm using SSLeay in embedded applications where
> > storage space is at premium.
> Exactly my problem.
This used to me my view (hence the lots of little files). I'll look at
breaking things up a bit more and making it dynamic. I'll also look at
having the DH/DSA/RSA stuff in the SSL part of the library dynamic.
If you want small code, also try compiling with NO_ERR. This will change the
error reporting stuff to not include line number, file names, or the error
strings, which reduces size by quite a bit. If you have string pooling in
your compiler, this is not such an issue. For the current SSLeay, the striped
ssleay binraries are
text data bss dec hex filename
470392 121502 6944 598838 92336 ssleay.old
465368 99266 6952 571586 8b8c2 sskeay.new
(these are a few new ciphers linked into the ssleay binrary which would be
left out of an embeded application...)
eric
+-------------------------------------------------------------------------+
| Administrative requests should be sent to [EMAIL PROTECTED] |
| List service provided by Open Software Associates, http://www.osa.com/ |
+-------------------------------------------------------------------------+
