extra-cmake-modules.git, branch v1.2.1 hurd extra-cmake-modules.git Fix calls to qmake 2014-09-11T22:02:20+00:00 Aleix Pol aleixpol@kde.org 2014-09-11T22:02:20+00:00 ad1406644fb51ee0097095915ffab099718268e0 We were keeping the \n after the path, and it would crash in some places. Strip the whitespaces in both ends. Reviewed by Rohan Garg 
We were keeping the \n after the path, and it would crash in some
places. Strip the whitespaces in both ends.

Reviewed by Rohan Garg
Fix fallout from recent ECM patches 2014-09-11T20:00:00+00:00 Alex Merry alex.merry@kde.org 2014-09-11T20:00:00+00:00 f8609e8b64fd9170aa1444ad4e2f6d6d759e9050 KDE modules cannot assume the normal ECM modules are in the CMake module path, and CMAKE_INSTALL_IMPORTS_INSTALL_DIR / QTQUICKIMPORTSDIR was not set correctly. Also, ECMQueryQmake.cmake used a deprecated CMake command (exec_program). 
KDE modules cannot assume the normal ECM modules are in the CMake module
path, and CMAKE_INSTALL_IMPORTS_INSTALL_DIR / QTQUICKIMPORTSDIR was not
set correctly. Also, ECMQueryQmake.cmake used a deprecated CMake command
(exec_program).
Make code coverage possible in any KDE project 2014-09-11T09:03:55+00:00 Aleix Pol aleixpol@kde.org 2014-09-11T08:48:06+00:00 6ab50fa9e27c4710beb2641fd510dfce08cc2719 Introduces a BUILD_COVERAGE option from a ECMCoverageOption file so that projects can easily enable code coverage in their applications. Furthermore, KDECompilerSettings does include that by default, so all proper KDE projects have the option by default. REVIEW: 120118 
Introduces a BUILD_COVERAGE option from a ECMCoverageOption file so that
projects can easily enable code coverage in their applications.
Furthermore, KDECompilerSettings does include that by default, so all
proper KDE projects have the option by default.

REVIEW: 120118
Add compiler sanitizers support 2014-09-10T22:58:20+00:00 Mathieu Tarral mathieu.tarral@gmail.com 2014-09-10T22:57:50+00:00 a4ae63d26665c814a452d4949a067a6bab45152e REVIEW: 119968 
REVIEW: 119968
Introduce ECMGeneratePkgConfigFile 2014-09-10T08:03:25+00:00 Aleix Pol aleixpol@kde.org 2014-09-10T08:03:25+00:00 f5f4d572ba0904a5c5c52a0de710112b953767ce A new module has been introduced to generate pkgconfig files from cmake projects. REVIEW: 119798 
A new module has been introduced to generate pkgconfig files from
cmake projects.

REVIEW: 119798
Upgrade ECM version for 1.2.0 release. 2014-09-05T22:20:45+00:00 l10n daemon script scripty@kde.org 2014-09-05T22:20:45+00:00 a9e748d1b56470769450483baa5c16079ed99871 






Fixup a minor typo from the last commit
2014-09-05T09:11:36+00:00

Rohan Garg
rohan16garg@gmail.com

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

6be0fc90efcfaa310ee95d342c2b57855a12c4e3












Fix ECM to use qmake instead of hardcoding plugin install dirs
2014-09-03T12:28:14+00:00

Rohan Garg
rohan16garg@gmail.com

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

96e7fb9969b761cce956a3500ede3b1c6cb29c65

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





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

Raphael Kubo da Costa
rakuco@FreeBSD.org

2014-08-10T17:30:20+00:00

5d6171f4c3a3f87e4e7114131304028b8b54941b

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





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

Patrick von Reth
vonreth@kde.org

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

8cf3d0ae17b84adb484c4a32e4475a45fa51848a