From: Jeff Trawick <trawick@apache.org>
Date: Sat, 29 Mar 2014 17:03:00 +0000 (+0000)
Subject: Describe issue with multiple OpenSSL installs
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=00e75eba5243c52fa81c4b8a40f3059c79c99bb2;p=thirdparty%2Fapache%2Fhttpd.git

Describe issue with multiple OpenSSL installs

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1583027 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/README.cmake b/README.cmake
index 3f1e72ada47..1b0589b3af4 100644
--- a/README.cmake
+++ b/README.cmake
@@ -59,6 +59,25 @@ enabled:
 * openssl (mod_ssl and https support for ab)
 * zlib (mod_deflate)
 
+OpenSSL
+-------
+
+If you have a binary install of OpenSSL in a well-known directory (e.g.,
+%HOME%\OpenSSL-Win64) and you wish to build httpd against a different
+install of OpenSSL, the cmake build may unexpectedly select OpenSSL
+libraries in the well-known directory even if the expected include files
+are used.  Check the cmake output from your httpd build to confirm that
+the expected OpenSSL libraries and include files are used.
+
+The cmake FindOpenSSL module searches for OpenSSL libraries in a "VC"
+subdirectory of the OpenSSL install with filenames that indicate the build
+type (e.g., "<PREFIX>/lib/VC/ssleay32MD.lib"); defining CMAKE_PREFIX_PATH
+or OPENSSL_ROOT_DIR or even OPENSSL_LIBRARIES does not circumvent finding
+these libraries.
+
+To work around this issue, rename the well-known OpenSSL directory while
+building httpd.  Let us know if you find a better solution.
+
 How to build
 ------------