This is a bit hacky because the arg parser
will read it as argument '-q' with the specified
value 'mljsdebugger...'. Shouldn't be a problem
though because we don't really read the value on
our own.
It is not possible to extract data from the QDBusArgument
anymore. So let's just make the NotificationImage become a
QDBusArgument itself and add it directly as hint.
* 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.
This makes the annoying hasBeenShown() check in each apply()
and reset() implementation unnecessary. It should not break
anything because if the page hasn't been shown there is nothing
to reset/apply anyways.
* 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
English translation files are built-in and usually only used
for plural forms. Hence the files are often empty and the
warnings about them are more misleading than helpful most of
the time.
TODO: Find a way to distinguish between translations
which are supposed to be empty and missing/invalid
translations.