From 4fa3f08fee253020ea152e11ff1f6fdcab79424f Mon Sep 17 00:00:00 2001 From: Richard Levitte Date: Sat, 22 Oct 2016 00:49:27 +0200 Subject: [PATCH] Add some notes on shared library names on different platforms This is overdue since the addition of the unified build system Reviewed-by: Rich Salz (Merged from https://github.com/openssl/openssl/pull/1767) --- INSTALL | 29 +++++++++++++++++++++++++++-- 1 file changed, 27 insertions(+), 2 deletions(-) diff --git a/INSTALL b/INSTALL index a6e8ea6eba..de127df275 100644 --- a/INSTALL +++ b/INSTALL @@ -937,8 +937,8 @@ supported. If your platform does not provide pthreads or Windows threads then you should Configure with the "no-threads" option. - Note on shared libraries - ------------------------ + Notes on shared libraries + ------------------------- For most systems the OpenSSL Configure script knows what is needed to build shared libraries for libcrypto and libssl. On these systems @@ -947,6 +947,31 @@ where OpenSSL does not know how to build shared libraries the "no-shared" option will be forced and only static libraries will be created. + Shared libraries are named a little differently on different platforms. + One way or another, they all have the major OpenSSL version number as + part of the file name, i.e. for OpenSSL 1.1.x, 1.1 is somehow part of + the name. + + On most POSIXly platforms, shared libraries are named libcrypto.so.1.1 + and libssl.so.1.1. + + on Cygwin, shared libraries are named cygcrypto-1.1.dll and cygssl-1.1.dll + with import libraries libcrypto.dll.a and libssl.dll.a. + + On Windows build with MSVC or using MingW, shared libraries are named + libcrypto-1_1.dll and libssl-1_1.dll for 32-bit Windows, libcrypto-1_1-x64.dll + and libssl-1_1-x64.dll for 64-bit x86_64 Windows, and libcrypto-1_1-ia64.dll + and libssl-1_1-ia64.dll for IA64 Windows. With MSVC, the import libraries + are named libcrypto.lib and libssl.lib, while with MingW, they are named + libcrypto.dll.a and libddl.dll.a. + + On VMS, shareable images (VMS speak for shared libraries) are named + ossl$libcrypto0101_shr.exe and ossl$libssl0101_shr.exe. However, when + OpenSSL is specifically built for 32-bit pointers, the shareable images + are named ossl$libcrypto0101_shr32.exe and ossl$libssl0101_shr32.exe + instead, and when built for 64-bit pointers, they are named + ossl$libcrypto0101_shr64.exe and ossl$libssl0101_shr64.exe. + Note on random number generation --------------------------------