Hi! I am very inexperienced with C so please bear with my question:
I am working on a project which uses a third-party library LibRTMP which in turns uses OpenSSL (v0.9.8m). I managed to compile all three components (OpenSSL, LibRTMP and my project) using MinGW+MSYS on Windows XP. My problem is that I end up with a static dependency on DLL files cryptoeay32-0.9.8.dll and ssleay32-0.9.8.dll, which is about the worst outcome for me. I would like to remove that dependency and get one of these (in order of preference): 1) OpenSSL (libCrypto) linked into my executable (that is, no DLL dependency at all, at the cost of a larger .exe file). 2) OpenSSL (libCrypto) dynamically (on demand, not on load) linked to cryptoeay32.dll/ssleay32.dll (no version numbers within filenames). 3) OpenSSL (libCrypto) statically (on load) linked to cryptoeay32.dll/ssleay32.dll (no version numbers within filenames). 4) OpenSSL (libCrypto) dynamically (on demand, not on load) linked to cryptoeay32-0.9.8.dll/ssleay32-0.9.8.dll. Unfortunately, I can't find a way to do it. My OpenSSL compile (performed with "Configure mingw shared") did create two versions of each library file (libcrypto.a, libcrypto.dll.a, libssl.a, libssl.dll.a), and I assume the dll-less libraries could be included within the exefile's code somehow, presumably using some clever #include - but which one? If anyone could help, I would appreciate it. Thanks, Pepak ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
