extra-cmake-modules.git/kde-modules, branch v5.30.0-rc1

Revert "Enable -Wsuggest-override for g++ >= 5.0.0"

2017-01-03T00:25:51+00:00

This reverts commit d1d637fadd6dad68995d44101250ebbc3307ed0b.

This is far too noisy.

The correct steps for this kind of change are:

* Enable the warning locally
* Take the action recommended by the warning in the code, and push the
  result
* Push the warning on everyone to enforce that the code stays fixed for
  the future

appstreamtest: handle non-installed programs

2016-12-30T07:41:16+00:00

Summary:
If you just built the software without installing it and then run ctest,
this will systematically fail while trying to read install_manifest.txt.
With this patch this case is now handled gracefully, not forcing to
install to have a test suite which fully passes.

Reviewers: #frameworks, apol

Differential Revision: https://phabricator.kde.org/D3860

Enable -Wsuggest-override for g++ >= 5.0.0

2016-12-29T23:48:29+00:00

REVIEW: 129724

Enable colored warnings in ninja's output

2016-12-29T11:18:55+00:00

Summary:
Colored compiler warnings in ninja output only work with the
`-fdiagnostics-color=always` flag.
See https://github.com/ninja-build/ninja/issues/814 for a rationale.

This commit adds such flag in ecm for gcc >= 4.9 and clang >= 3.5,
and only if the CMAKE_GENERATOR is Ninja.

Test Plan: ninja+gcc and ninja+clang now show nice colored compiler warnings.

Reviewers: #frameworks

Differential Revision: https://phabricator.kde.org/D3733

Never use -Wl,--no-undefined on Mac (APPLE).

2016-12-11T18:03:31+00:00

While unusual it is not impossible to use GCC on Macs, esp. not when
using older OS X versions. Intel also makes compilers for Mac, so it may
in fact be better to rewrite the check ((GNU or Clang or Intel) IF NOT
(APPLE or WIN32)).

Accept AppleClang as an alternative to Clang

2016-12-10T14:17:15+00:00

Apple's clang v3.1 corresponds to clang 3.1 and started following the
Xcode versioning scheme from 4.4 onwards (though loosely). An overview
of the version correspondance can be found here:
https://gist.github.com/yamaya/2924292

Find the correct path to the cmake command

2016-12-03T20:25:10+00:00

Summary: When running tests with hardcoded `cmake`, it get's suffixed to the project's build path. Setting it with an absolute path ensures using the right cmake binary.

Test Plan: Compiled, installed. Used to generate tests for kdev-embedded. `cmake` binary is now prefixed with the absolute system path, and no longer with the project's build dir.

Reviewers: kfunk, #frameworks, apol

Reviewed By: kfunk, apol

Subscribers: kfunk

Differential Revision: https://phabricator.kde.org/D3568

Use commits.kde.org in links instead of now outdated quickgit.kde.org

2016-11-16T16:24:59+00:00

also correct link to clazy's README.md (former README)

Make KDECMakeSettings work with KDE_INSTALL_DIRS_NO_DEPRECATED

2016-11-05T09:56:07+00:00

REVIEW: 128806

Revert "Teach KDECompilerSettings about clang-cl, a mode of Clang compiler that simulates MSVC."

2016-10-08T09:00:45+00:00

This reverts commit 4b8e8dcc8856d8f438860783e7641d02d1c05630.