diff options
| author | Alexandru Croitor <alexandru.croitor@qt.io> | 2018-05-30 23:56:01 +0200 |
|---|---|---|
| committer | Alexandru Croitor <alexandru.croitor@qt.io> | 2018-05-31 08:58:24 +0000 |
| commit | 032cb10444f786a7ed0a9321395f398c992eb15d (patch) | |
| tree | 9b8bc6fa3bd4411f19f70354b106dd3cb3fa041c /sources/pyside2/CMakeLists.txt | |
| parent | ccddbd5f8e21e05290f04ac0bb2181d6cb90db49 (diff) | |
Don't pass -DFORCE_LIMITED_API=yes from setup.py unless asked for
It was weird seeing "-DFORCE_LIMITED_API=yes" being passed from
setup.py to CMake when "--limited-api" is not included on the
command line, and then seeing "-DFORCE_LIMITED_API=yes" with Python 2
builds. It gives the impression that maybe it could work with
Python 2.
Instead, don't pass "FORCE_LIMITED_API=yes" from setup.py by default
(but still pass it if it's present on the command line), and instead
default to "yes" within the CMake project themselves.
In the end nothing changes, limited API builds will still be default,
but at least it's not as confusing to see the
"-DFORCE_LIMITED_API=yes" lines for Python 2 builds in the CI log.
Change-Id: I08c863394dd148d88bec324a6cab35459d75303a
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
Diffstat (limited to 'sources/pyside2/CMakeLists.txt')
| -rw-r--r-- | sources/pyside2/CMakeLists.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sources/pyside2/CMakeLists.txt b/sources/pyside2/CMakeLists.txt index ee98d1d09..d5cf26612 100644 --- a/sources/pyside2/CMakeLists.txt +++ b/sources/pyside2/CMakeLists.txt @@ -90,7 +90,7 @@ else() set(PATH_SEP ":") endif() -option(FORCE_LIMITED_API "Enable the limited API." "no") +option(FORCE_LIMITED_API "Enable the limited API." "yes") set(PYTHON_LIMITED_API 0) if(FORCE_LIMITED_API STREQUAL "yes") |