Only handle QTPLUGIN when linking against static Qt
Usage of QTPLUGIN implies static Qt, so only handle it when that is true so user projects do not need to scope it if they support linking against both static and shared Qt. Change-Id: I011b4672bac122d7d64d8f2fc0e41ca7e5251dfc Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
This commit is contained in:
parent
21105e7138
commit
db4aa4d1d5
@ -35,7 +35,8 @@ plugin { #Qt plugins
|
||||
}
|
||||
}
|
||||
|
||||
QT_PLUGIN_VERIFY = QTPLUGIN DEPLOYMENT_PLUGIN
|
||||
QT_PLUGIN_VERIFY = DEPLOYMENT_PLUGIN
|
||||
contains(QT_CONFIG, static): QT_PLUGIN_VERIFY += QTPLUGIN
|
||||
for(QT_CURRENT_VERIFY, $$list($$QT_PLUGIN_VERIFY)) {
|
||||
for(QTPLUG, $$list($$lower($$unique($$QT_CURRENT_VERIFY)))) {
|
||||
# Check if the plugin is known to Qt. We can use this to determine
|
||||
|
Loading…
Reference in New Issue
Block a user