From db4aa4d1d56a37843d4f31194f4a452c86a26a11 Mon Sep 17 00:00:00 2001 From: Miikka Heikkinen Date: Fri, 7 Dec 2012 09:54:43 +0200 Subject: 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 --- mkspecs/features/qt.prf | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'mkspecs/features/qt.prf') diff --git a/mkspecs/features/qt.prf b/mkspecs/features/qt.prf index 586dae3981..443914e011 100644 --- a/mkspecs/features/qt.prf +++ b/mkspecs/features/qt.prf @@ -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 -- cgit v1.2.3