Ok, so we are using OpenSSL in one of our new products, and I have taken
quite a bit of time to make sure that all of our sources (including all the
third party libraries we license, etc) can build in a separate object
directory. This is really handy for building debug and release versions in
parallel trees from the exact same source, etc, etc. And it is is fairly
trivial to do, and should even work with all the make variants out there.
We also use libtool to build all of our stuff as shared libraries when
possible.
Getting OpenSSL to integrate into this is a bit of a pain in the #%!@.
So my question is: would people be willing to throw out all the Configure
and halfway autoconf support if I blew a few hours over the next couple of
days to completely rework it? This would buy us shared library support as
well, which I notice was on the todo list in the status reports.
I'm not sure how this would impact the win32 port, but the autoconf
maintainer is planning on support windows in the next major release
(according to some email quite a few months ago - not sure what the current
status is).
Any screams of agony out there? Hurrahs? :)
-Bill P.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
