Summary:
the wiki page says the readme is duplicated into the wiki.

so, what we end up with is either

- they end up out of sync
- someone gets real angry because the wiki needs format markup while the
  readme must not have markup
- someone doesn't get angry and simply copies either markup or nomarkup to
  the respectively unsuitable target

it's an unsustainable situation... so instead let's point the readme to
the wiki and consider that the place where the documentation is maintained

Subscribers: kde-frameworks-devel

Tags: #frameworks

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

Summary:
the previous logging tech got kind of defunct in 2014 (to the point where
it was basically qCDebug). seeing as no one really complained it seems
reasonable to just move to qCDebug instead and make use of category filters
and other qdebug goodness (such as system logging facilities for the
various platforms)

- new logging category kf5.kconfig.update; at info level by default (i.e.
  unless otherwise configured kconf_update is now silent)
- --debug cmdline option now also attempts to force-enable the debug mode
  on that category (and debugs that attempt in of itself, so we don't get
  confused by categories magically getting enabled).
- all log() calls are now qCDebug calls
- all logFileErorr() calls (which was context-sensitive to the .upd file
  parsing) have been changed to qCDebugFile
- qCDebugFile is a new *macro* wrapping around qCDebug to give it file
  context
- everything is now qCDebug instead of qDebug
- arguments updated to drop excess quoting and spaces to reduce "noise"

https://markmail.org/thread/ofaeqcabguxyohyb

Test Plan: updater still works and debugs when debug is enabled

Reviewers: apol, aacid, #frameworks

Subscribers: kde-frameworks-devel

Tags: #frameworks

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

Summary: compile without foreach

Test Plan: Unittest Ok as previously

Reviewers: dfaure

Reviewed By: dfaure

Subscribers: kde-frameworks-devel

Tags: #frameworks

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

they are unused, but if anyone would use them things would go wrong, so
protect us from it

Summary:
This way if another cmake project imports it when cross-compiling, it
can be executed.

Reviewers: #frameworks

Tags: #frameworks

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

Summary:
This is particularly useful for cross-compilation, where we only need the
kconfig_compiler on the host system.

Reviewers: #frameworks, apol, aacid

Reviewed By: aacid

Subscribers: aacid

Tags: #frameworks

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