summaryrefslogtreecommitdiff
path: root/README.cmake
diff options
context:
space:
mode:
authorJeff Trawick <trawick@apache.org>2014-03-29 17:03:00 +0000
committerJeff Trawick <trawick@apache.org>2014-03-29 17:03:00 +0000
commit8db4e52b48a2fa105b580054aaaf7678ef70e79f (patch)
treeed4b27fcd3e0a766bb5f021a5d6fe26402b45334 /README.cmake
parent9f59d4c14ca6a2c18e20d1376d88523148c52944 (diff)
downloadhttpd-8db4e52b48a2fa105b580054aaaf7678ef70e79f.tar.gz
Describe issue with multiple OpenSSL installs
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1583027 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'README.cmake')
-rw-r--r--README.cmake19
1 files changed, 19 insertions, 0 deletions
diff --git a/README.cmake b/README.cmake
index 3f1e72ada4..1b0589b3af 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
------------