<feed xmlns='http://www.w3.org/2005/Atom'>
<title>extra-cmake-modules.git/kde-modules, branch v5.32.0-rc1</title>
<subtitle>hurd extra-cmake-modules.git</subtitle>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/'/>
<entry>
<title>Fix ENABLE_CLAZY on Windows</title>
<updated>2017-02-01T13:22:22+00:00</updated>
<author>
<name>Hannah von Reth</name>
<email>vonreth@kde.org</email>
</author>
<published>2017-02-01T13:20:22+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=16a148feda4e9761e2644972c4623b355ffa7e92'/>
<id>16a148feda4e9761e2644972c4623b355ffa7e92</id>
<content type='text'>
Summary:

Reviewers: smartins, alexmerry, apol

Reviewed By: apol

Subscribers: #windows, #build_system, #frameworks

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D4389
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Summary:

Reviewers: smartins, alexmerry, apol

Reviewed By: apol

Subscribers: #windows, #build_system, #frameworks

Tags: #frameworks, #build_system

Differential Revision: https://phabricator.kde.org/D4389
</pre>
</div>
</content>
</entry>
<entry>
<title>Enable -Wsuggest-override for g++ &gt;= 5.0.0</title>
<updated>2017-01-23T19:04:47+00:00</updated>
<author>
<name>Albert Astals Cid</name>
<email>aacid@kde.org</email>
</author>
<published>2017-01-23T19:04:47+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=faeb56f8137d738d1dfbc1fcfbbacd1e8caeb6f0'/>
<id>faeb56f8137d738d1dfbc1fcfbbacd1e8caeb6f0</id>
<content type='text'>
REVIEW: 129724
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
REVIEW: 129724
</pre>
</div>
</content>
</entry>
<entry>
<title>Pass -fno-operator-names when supported</title>
<updated>2017-01-16T07:46:43+00:00</updated>
<author>
<name>Kevin Funk</name>
<email>kfunk@kde.org</email>
</author>
<published>2016-12-29T11:23:20+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=a5f3a76e14799c68b5e8f74e375baa5f6f6ab4dc'/>
<id>a5f3a76e14799c68b5e8f74e375baa5f6f6ab4dc</id>
<content type='text'>
Summary:
Disables alternative tokens for &amp;&amp;, ||, etc.. They're are not supported
by MSVC out of the box, thus using them will limit the portability of
the code. There *are* options to make alternative tokens available under
MSVC [1], but I think we shouldn't promote the usage of them.

From the GCC documentation:
-fno-operator-names: Do not treat the operator name keywords and,
bitand, bitor, compl, not, or and xor as synonyms as keywords.

[1] http://stackoverflow.com/questions/555505/when-were-the-and-and-or-alternative-tokens-introduced-in-c

Reviewers: #frameworks, #buildsystem, ivan

Reviewed By: ivan

Subscribers: rakuco, elvisangelaccio

Differential Revision: https://phabricator.kde.org/D3850
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Summary:
Disables alternative tokens for &amp;&amp;, ||, etc.. They're are not supported
by MSVC out of the box, thus using them will limit the portability of
the code. There *are* options to make alternative tokens available under
MSVC [1], but I think we shouldn't promote the usage of them.

From the GCC documentation:
-fno-operator-names: Do not treat the operator name keywords and,
bitand, bitor, compl, not, or and xor as synonyms as keywords.

[1] http://stackoverflow.com/questions/555505/when-were-the-and-and-or-alternative-tokens-introduced-in-c

Reviewers: #frameworks, #buildsystem, ivan

Reviewed By: ivan

Subscribers: rakuco, elvisangelaccio

Differential Revision: https://phabricator.kde.org/D3850
</pre>
</div>
</content>
</entry>
<entry>
<title>Revert "Enable -Wsuggest-override for g++ &gt;= 5.0.0"</title>
<updated>2017-01-03T00:25:51+00:00</updated>
<author>
<name>Stephen Kelly</name>
<email>steveire@gmail.com</email>
</author>
<published>2017-01-03T00:25:51+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=4a986d8db8e9b594679b008fd70b818ef2ad94a5'/>
<id>4a986d8db8e9b594679b008fd70b818ef2ad94a5</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
<entry>
<title>appstreamtest: handle non-installed programs</title>
<updated>2016-12-30T07:41:16+00:00</updated>
<author>
<name>Kevin Ottens</name>
<email>ervin@kde.org</email>
</author>
<published>2016-12-29T15:39:25+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=5ed7ba07e4f382f4e07e2de7feca33c16a2793f7'/>
<id>5ed7ba07e4f382f4e07e2de7feca33c16a2793f7</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
<entry>
<title>Enable -Wsuggest-override for g++ &gt;= 5.0.0</title>
<updated>2016-12-29T23:48:29+00:00</updated>
<author>
<name>Albert Astals Cid</name>
<email>aacid@kde.org</email>
</author>
<published>2016-12-29T23:47:57+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=d1d637fadd6dad68995d44101250ebbc3307ed0b'/>
<id>d1d637fadd6dad68995d44101250ebbc3307ed0b</id>
<content type='text'>
REVIEW: 129724
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
REVIEW: 129724
</pre>
</div>
</content>
</entry>
<entry>
<title>Enable colored warnings in ninja's output</title>
<updated>2016-12-29T11:18:55+00:00</updated>
<author>
<name>Elvis Angelaccio</name>
<email>elvis.angelaccio@kde.org</email>
</author>
<published>2016-12-29T11:18:55+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=dc525a42ae70a68d67aa49d6453d4b6de4ecb561'/>
<id>dc525a42ae70a68d67aa49d6453d4b6de4ecb561</id>
<content type='text'>
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 &gt;= 4.9 and clang &gt;= 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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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 &gt;= 4.9 and clang &gt;= 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
</pre>
</div>
</content>
</entry>
<entry>
<title>Never use -Wl,--no-undefined on Mac (APPLE).</title>
<updated>2016-12-11T18:03:31+00:00</updated>
<author>
<name>R.J.V. Bertin</name>
<email>rjvbertin@gmail.com</email>
</author>
<published>2016-12-11T18:03:31+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=187d8881a6a0c33f50eb65689aa1dd74a8d107a4'/>
<id>187d8881a6a0c33f50eb65689aa1dd74a8d107a4</id>
<content type='text'>
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)).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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)).
</pre>
</div>
</content>
</entry>
<entry>
<title>Accept AppleClang as an alternative to Clang</title>
<updated>2016-12-10T14:17:15+00:00</updated>
<author>
<name>R.J.V. Bertin</name>
<email>rjvbertin@gmail.com</email>
</author>
<published>2016-12-10T14:17:15+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=ea6d3a16bd6771b8d52641e27a3593cf580adb1f'/>
<id>ea6d3a16bd6771b8d52641e27a3593cf580adb1f</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
<entry>
<title>Find the correct path to the cmake command</title>
<updated>2016-12-03T20:25:10+00:00</updated>
<author>
<name>Ovidiu-Florin BOGDAN</name>
<email>ovidiu.b13@gmail.com</email>
</author>
<published>2016-12-02T10:44:34+00:00</published>
<link rel='alternate' type='text/html' href='https://netuse.dynamicmalloc.com/cgit/extra-cmake-modules.git/commit/?id=e630aa985494bcfccb5b5e722a32a4e77d581271'/>
<id>e630aa985494bcfccb5b5e722a32a4e77d581271</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
</feed>
