aboutsummaryrefslogtreecommitdiffstats
path: root/setup.py
diff options
context:
space:
mode:
authorAlexandru Croitor <alexandru.croitor@qt.io>2018-06-21 21:09:25 +0200
committerAlexandru Croitor <alexandru.croitor@qt.io>2018-06-22 09:02:37 +0000
commit87942459a27465439eb85d083545bfe0fddf2ff4 (patch)
tree6fe628a0da498985d351ff52c6ac48e5f4983b73 /setup.py
parentaa75437f9119d997dd290471ac3e2cc88ca88bf1 (diff)
Don't package OpenSSL libraries on Windows Coin builds
This is due to http://doc.qt.io/qt-5/ssl.html#import-and-export-restrictions A user may still pass --openssl option if they wish to package the libraries for their own local build. Task-number: PYSIDE-715 Change-Id: Iadade188ffa13decf03bc21b016718176f6ead6e Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io> Reviewed-by: Alex Blasche <alexander.blasche@qt.io> Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
Diffstat (limited to 'setup.py')
-rw-r--r--setup.py11
1 files changed, 9 insertions, 2 deletions
diff --git a/setup.py b/setup.py
index 813d7c01..a24e656e 100644
--- a/setup.py
+++ b/setup.py
@@ -60,6 +60,8 @@ For Windows, if OpenSSL support is required, it's necessary to specify
the directory path that contains the OpenSSL shared libraries
"libeay32.dll" and "ssleay32.dll", for example:
--openssl=C:\OpenSSL-Win64\bin
+This will make sure that the libraries are copied into the PySide2
+package and are found by the QtNetwork module.
ADDITIONAL OPTIONS:
@@ -150,9 +152,14 @@ REQUIREMENTS:
OPTIONAL:
* OpenSSL:
- Specifying the --openssl option is only required on Windows.
+ Specifying the --openssl option only affects Windows.
It is a no-op for other platforms.
+ Please note that official Windows packages do not ship the
+ OpenSSL libraries due to import / export restrictions as
+ described in
+ http://doc.qt.io/qt-5/ssl.html#import-and-export-restrictions
+
You can specify the location of the OpenSSL DLLs with the
following option:
--openssl=</path/to/openssl/bin-directory>.
@@ -177,7 +184,7 @@ OPTIONAL:
shared libraries, are not currently compatible with
standalone PySide2 packages.
- (*) Revised on 23.03.2018
+ (*) Revised on 21.06.2018
* macOS SDK:
You can specify which macOS SDK should be used for compilation with