Hi! I'm writing a distributed application that supports several platforms (e.g. linux, solaris, solarisx86, and win32).
Because each of these different platforms has varying degrees of native support for openssl and platforms often have different versions installed, I would like to include libssl.so and libcrypto.so with my application so as to ensure each installation is using a consistent version. However, I'm running into difficulties because my distribution uses a single flat directory with binaries named for appname-platform. For example, appname-linux, appname-win32, appname-solaris, etc. Consequently, I cannot just drop compiled versions of libssl.so into the same directory w/o re-naming them to be libssl-linux.so, and so on. Because the shared libraries have an soname in them, renaming the library file causes the application to fail to load because the loader is still looking for libssl.so and not libssl-linux.so. Is there a way to rename the soname in the openssl build? I've been trying to read through the SSL/crypto makefiles but my attempts to set SHLIB_SUFFIX do not seem to be working. Lastly, has anyone faced this problem before and solved it? I hate to re-invent the wheel. Static linking does not seem appropriate as I cant get my app to statically link against libssl/libcrypto (I get lots of undefined symbol errors) and statically linking tends to not work well across platforms that have different versions of underlying libraries. Thanks for any tips, suggestions, or answers. Bobby ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
