diff options
author | Paul Kehrer <paul.l.kehrer@gmail.com> | 2017-02-09 13:53:44 +0800 |
---|---|---|
committer | Alex Gaynor <alex.gaynor@gmail.com> | 2017-02-09 00:53:44 -0500 |
commit | f19fef16287a767f133182337e93c478dd48ea93 (patch) | |
tree | 3889967583a9a414b7559a38f147a1a6c762deb1 /docs | |
parent | 7a13085afce1415c0524a5dc5b94c98e3d6d7b7d (diff) | |
download | cryptography-f19fef16287a767f133182337e93c478dd48ea93.tar.gz cryptography-f19fef16287a767f133182337e93c478dd48ea93.tar.bz2 cryptography-f19fef16287a767f133182337e93c478dd48ea93.zip |
support defining which windows libraries to link with an env var (#3356)
* support defining which windows libraries to link with an env var
CRYPTOGRAPHY_WINDOWS_LIBRARIES is your new friend
* add some docs
* change to CRYPTOGRAPHY_WINDOWS_LINK_OPENSSL110
* lib prefixing is not a thing msvc does, right
Diffstat (limited to 'docs')
-rw-r--r-- | docs/installation.rst | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/docs/installation.rst b/docs/installation.rst index 2c24d35d..a1b5642d 100644 --- a/docs/installation.rst +++ b/docs/installation.rst @@ -50,7 +50,7 @@ If you prefer to compile it yourself you'll need to have OpenSSL installed. You can compile OpenSSL yourself as well or use the binaries we build for our release infrastructure (`openssl-release`_). Be sure to download the proper version for your architecture and Python (2010 works for Python 2.6, 2.7, 3.3, -and 3.4 while 2015 is required for 3.5). Wherever you place your copy +and 3.4 while 2015 is required for 3.5 and above). Wherever you place your copy of OpenSSL you'll need to set the ``LIB`` and ``INCLUDE`` environment variables to include the proper locations. For example: @@ -59,8 +59,14 @@ to include the proper locations. For example: C:\> \path\to\vcvarsall.bat x86_amd64 C:\> set LIB=C:\OpenSSL-win64\lib;%LIB% C:\> set INCLUDE=C:\OpenSSL-win64\include;%INCLUDE% + C:\> set CRYPTOGRAPHY_WINDOWS_LINK_OPENSSL110=1 C:\> pip install cryptography +As of OpenSSL 1.1.0 the library names have changed from ``libeay32`` and +``ssleay32`` to ``libcrypto`` and ``libssl`` (matching their names on all other +platforms). Due to this change when linking against 1.1.0 you **must** set +``CRYPTOGRAPHY_WINDOWS_LINK_OPENSSL110`` or else installation will fail. + If you need to rebuild ``cryptography`` for any reason be sure to clear the local `wheel cache`_. |