In article <[EMAIL PROTECTED]> you wrote:
> 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.
Should work on all platforms. Because I've added the DSO support for all those
platforms Apache currently supports. And all of them supports it this way as
far as I can remember. So, we just have to add two more variables to the
Configure stuff: One holding the PIC flags for the compiler, the other holding
the shared lib flags for the linker. The details we can rip out of our Apache
src/Configure script. The main problem is just that the PIC flag depends on
the used C compiler (-fPIC for GCC vs. -kPIC for SVR4, etc).
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
