Ben Laurie wrote:
>
> Ralf S. Engelschall wrote:
> > The shared library support in SSLeay/OpenSSL is still very ugly and
> > inconsistent. Actually in the future is should be integrated back into the
> > Configure script and the Makefiles as it's the case for Apache. When you've
> > good suggestions send them to us. My current idea is at least a "shlib" or
> > "dso" argument for Configure which triggers the generation of libcrypto.so and
> > libssl.so instead of libcrypto.a and libssl.a. Ben, you're already working the
> > Configure stuff, have you perhaos done something in this area, too?
>
> No, I'm afraid not. But whatever we do, please, let's try to keep it
> simple!
>
I did get shared libraries going under linux manually and it wasn't too
painful. What I ended up doing was building the regular library but with
the -fPIC flag then using some linker option to take the *.a files and
link them all together into the .so library file.
I don't know if this would work on other platforms.
Steve.
--
Dr Stephen N. Henson. UK based freelance Cryptographic Consultant.
For info see homepage at http://www.drh-consultancy.demon.co.uk/
Email: [EMAIL PROTECTED]
NOTE NEW (13/12/98) PGP key: via homepage.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
