Hi.
Platform: NT4.0
For various reasons we want to link statically against the openssl libs.
In one of our programs there is no need to establish any network connections,
but, never the less we want to create a SSL_CTX object. The reason is that we
want to ask it for the available cipher suites. Code borrowed from one of the
files in the distribution.
This seems to pull in the ssl_lib.c compilation unit, which in turn pulls
in bss_sock.c (through the use of BIO_s_socket() from within SSL_set_fd()).
Finally, bss_sock.c requires network support, which causes winsock2.dll to
be loaded, quite unnecessarily.
It would be useful to move the functions surrounded with "#ifndef
NO_SOCK/#endif" to a separate compilation unit. This would reduce these
external dependencies, at least in my case.
/ Mats Nilsson
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
