* Set the default icon theme when applying Qt settings and the "system"
theme is supposed to be used but none could be determined by Qt
* Use a bundled icon theme depending on whether the current palette is
light or dark
* Apply the default not only under Windows anymore; supposedly this makes
sense under any platform where Qt cannot determine the icon theme for us
* Detect a static Qt build and link against Qt plugins automatically in
that case (without the necassity to set `STATIC_LINKAGE`)
* Add offscreen support on UNIX platforms as it is useful for testing on
headless systems
* Add wayland support if available
* Populate `QT_TEST_LIBRARIES` in case we're not building an app because
the plugins are still required when building tests
This Qt release "pluginized" the backends for TLS support so we need to
make sure to link against at least one TLS plugin since all of my
applications which use Qt Network expect TLS to work.
When cross compiling with Qt 5 the QT_HOST_PATH variable might
be set as well but the module might not be installed within the
host path. So let's do the usual lookup first and fallback to
QT_HOST_PATH only if that doesn't work.
The variables provided by Qt 6 might just contain a relative path. This
change adds an extra function resolve these via CMAKE_PREFIX_PATH and
CMAKE_FIND_ROOT_PATH.
When adding source files to the _FILES variables conditionally
those are so far not being formatted or translated. Adding
these files at least to the EXCLUDED_FILES will fix this.
Replaces DOC_ONLY_FILES which served the same purpose but was
limited to documentation.
* Fix missing "Vista style" in static, Qt 5.10 based
Windows build
* Required since the platform styles have been
"pluginized" in Qt 5.10
* See 4f3249f32d
* Which plugins should be included should only be decided
when building the final application and not before.
* Also prevents those libs from appearing in pkg-config
files.
* Only link targets using static Qt Gui/Widgets/Quick
against static plugins since currently only GUI-related
plugins are relevant
* Don't require to link explicitely against the related
module (eg. Qt Svg for the Svg icon engine) because the
imported target of the plugin should pull all required
dependencies
* Add option for linking against static Qt image format
plugins
* Link GUI applications using static Qt Gui/Widgets/Quick
against the static X11 platform integration plugin if it
is available
