[Kde-bindings] [buildsystem] [Bug 337462] CMake module fails to find PyQt
Raphael Kubo da Costa
rakuco at FreeBSD.org
Wed Jul 16 19:49:26 UTC 2014
https://bugs.kde.org/show_bug.cgi?id=337462
Raphael Kubo da Costa <rakuco at FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Latest Commit| |http://commits.kde.org/kdel
| |ibs/a7e47438d4e3469dc9df70d
| |613826cb360fc8d19
Status|ASSIGNED |RESOLVED
Version Fixed In| |4.14.0
--- Comment #1 from Raphael Kubo da Costa <rakuco at FreeBSD.org> ---
Git commit a7e47438d4e3469dc9df70d613826cb360fc8d19 by Raphael Kubo da Costa.
Committed on 16/07/2014 at 19:29.
Pushed by rkcosta into branch 'KDE/4.14'.
Make FindPyQt4 work with PyQt's new build system.
Since PyQt 4.10, PyQt.pyqtconfig is deprecated and not available unless
PyQt is built using the old configure script.
There is no direct replacement for it, as PyQt's new build system does
not provide as much information as before by design. Luckily, most of
the variables we are interested in can be obtained from PyQt's QtCore
module itself even if its old build system is used.
The only exception is pyqt_sip_dir, which cannot be determined at all if
pyqtconfig is not available. In this case, the most we can do is guess
the default path like QScintilla2 does, and fail if it does not exist.
The user then needs to specify it manually via CMake with something like
-DPYQT4_SIP_DIR=/usr/share/sip/PyQt4. To this effect, all variables set
by FindPyQt4.cmake have been made cache variables, which means their
values can be overriden by the user, thus ignoring the contents read via
FindPyQt.py.
FIXED-IN: 4.14.0
REVIEW: 119302
M +41 -17 cmake/modules/FindPyQt.py
M +27 -9 cmake/modules/FindPyQt4.cmake
http://commits.kde.org/kdelibs/a7e47438d4e3469dc9df70d613826cb360fc8d19
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Kde-bindings
mailing list