extra-cmake-modules.git, branch v1.2.0-rc2

Upgrade ECM version for 1.2.0 release.

2014-09-05T22:20:45+00:00

Fixup a minor typo from the last commit

2014-09-05T09:11:36+00:00

Fix ECM to use qmake instead of hardcoding plugin install dirs

2014-09-03T12:28:14+00:00

Packagers and other interested folks should pass -DKDE_INSTALL_USE_QT_SYS_PATHS=ON
when building in order to install various files to the same dir as the Qt5 install
dirs.

CCMAIL: kde-packagers@kde.org

REVIEW: 119901

KDECompilerSettings: Be more portable across libc's.

2014-08-12T22:12:11+00:00

Defining _XOPEN_SOURCE to 500 is too restrictive: it corresponds to
_POSIX_C_SOURCE 199506L, and hides several symbols that standard
libraries like libc++ expect to find, leading to errors like this on
FreeBSD:

  In file included from /tmp/attica/src/accountbalance.cpp:21:
  In file included from /tmp/attica/src/accountbalance.h:25:
  In file included from /usr/local/include/qt5/QtCore/QString:1:
  In file included from /usr/local/include/qt5/QtCore/qstring.h:50:
  In file included from /usr/include/c++/v1/string:437:
  In file included from /usr/include/c++/v1/string:437:
  /usr/include/c++/v1/cstdio:143:9: error: no member named 'snprintf' in the global namespace
  using ::snprintf;
        ~~^

This isn't a problem on Linux (actually, on systems using glibc) because
defining _GNU_SOURCE enables a lot more features that are not made
available on other libc implementations where it does not have any
effect.

Instead, stop defining _XOPEN_SOURCE at all and leave it up to the
platform to show or hide as many symbols as necessary if no
standards-related defines are set, and only set _GNU_SOURCE on systems
where it is actually meaningful (ie. systems using glibc).

REVIEW: 119696

also define _UNICODE on windows

2014-08-11T12:24:23+00:00

Remove Qt5 debugfull hack from ECMConfig.cmake

2014-08-06T20:21:44+00:00

The original purpose of this was to set the QT_NO_DEBUG macro if the old
DebugFull configuration was used. We got rid of DebugFull (instead just
using Debug), so it is no longer relevant, and this hack never belonged
in ECMConfig.cmake anyway (it should have been in KDECompilerSettings).

CHANGELOG: ECM now works when the required CMake version is set to
3.0.0 or higher, and does not require Qt5Core to be available.

BUG: 331849

REVIEW: 119588

increase ECM version for 1.1.0 release

2014-08-01T17:07:16+00:00

Make FindPyKDE4 work with PyQt's new build system.

2014-07-29T17:33:45+00:00

Since PyQt 4.10, PyQt.pyqtconfig is deprecated and not available unless
PyQt is built using the old configure script.

PyKDE4 itself has recently been adjusted to mimic PyQt itself and only
install its pykdeconfig module if pyqtconfig is present. Additionally,
information such as SIP flags and the directory where PyKDE's SIP files
are installed are now also provided in the
PyKDE4.kdecore.PYKDE_CONFIGURATION dict.

This commit completely rewrites FindPyKDE4.py to make it look like
FindPyQt.cmake after commit a7e4743: most of the information used by
FindPyKDE4.cmake is fetched from PyKDE4.kdecore, and we first try to
obtain the SIP flags and directory from pykdeconfig and, if it fails, we
use PYKDE_CONFIGURATION.

Furthermore, FindPyKDE4.py now only prints the variables that are
actually consumed by FindPyKDE4.cmake -- it is not possible to obtain
all the data provided by pykdeconfig in PYKDE_CONFIGURATION. We've also
stopped reading and setting PYKDE4_VERSION_TAG, since PyKDE4 stopped
setting a KDE tag in 2008 (and its value was 3_92_0 at the time).

(Forwardport kdelibs 4d29cf8)

Fix FindPyQt.py

2014-07-24T05:54:16+00:00

sys.prefix should be used instead of sys.platform

Forward port of kdelibs commit 8b1abe25dcf243cd2cdf23dff7272aca921292ae

FindPyQt4: Use PATH, not FILEPATH.

2014-07-20T17:54:04+00:00

PYQT4_SIP_DIR is a directory, not a file.

Forwardport of kdelibs/37f31f9ce39569a1096e5a04b6679a91e6ae18fe.