GitLab

Previously, interrupting a module build during the build was not treated
as a build failure, so the module's persistent options were not changed.
In the normal scenario this means the module's last build was remembered
as a success. Then by default, when you'd go to rebuild the module right
after, the build would be skipped because the source didn't change.

BUG:289754

When a Ninja-based generator is in use, we can look for its "ninja: no
work to do" message to know that the build phase did nothing.

In this situation, there's no point to installing, so why bother.

This has an additional improvement as well, we don't bother *uninstall*
when use-clean-install is set just to reinstall the same files.

This is at best a heuristic as it's possible that a changed dependency
library that is not part of the source repo could influence the binary
that is built.  In this situation ninja would report no work to do even
though the binary would change.  So I also tell the user how to force an
install (by forcing the build to do work using --refresh-build, other
methods might work as well).

Fixes #92.

Previously we just returned a boolean flag that throws out the rest of
the results object. Of course the object itself had only a bool but this
enables us to return more metadata and make decisions based on that,
such as whether the build did any work (which can influence a decision
to install or not).

A glib change caused tests/examples from telepathy-qt to fail to build.
This has since been fixed but seeing as how we're only building this for
the library, let's disable examples. I keep tests enabled for now but
let a comment that can be removed to disable those too.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Makes a bunch more things already enabled in here actually build.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In preparation of the same being done on the KF6 CI.

This causes the default CMake options to be overridden and in my case
the KF6 KActvities build used Qt5, because the -DBUILD_WITH_QT6=ON was not used.

We actually do not need the Cmake options at all, because BUILD_TESTING is handled by ECM
and the check if exceptions are needed is done as part of KActivities.

Louis Moureaux authored May 21, 2022 and Alexander Lohnau committed May 21, 2022

These packages aren't provided by Kde, but are required to build Plasma and
PowerDevil.