From 6944c012001dc3ad9956945934662d5621b11dc2 Mon Sep 17 00:00:00 2001
From: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
Date: Mon, 4 Feb 2013 12:10:13 +0100
Subject: export QT_CONFIG instead of CONFIG to .pc files

users need access to the Qt configuration, not some internals of
module's build system.

Change-Id: Ife3f668282969d444282d57152c11ed0f741076f
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
---
 mkspecs/features/qt_module.prf | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

(limited to 'mkspecs')

diff --git a/mkspecs/features/qt_module.prf b/mkspecs/features/qt_module.prf
index 8dce2634ca..fa3bea35ab 100644
--- a/mkspecs/features/qt_module.prf
+++ b/mkspecs/features/qt_module.prf
@@ -172,9 +172,8 @@ win32 {
 
 TARGET = $$qtLibraryTarget($$TARGET$$QT_LIBINFIX) #do this towards the end
 
-# Provides useful info normally only contained in the internal .qmake.cache file
 qt_conf.name = qt_config
-qt_conf.variable = CONFIG
+qt_conf.variable = QT_CONFIG
 QMAKE_PKGCONFIG_VARIABLES += qt_conf
 
 load(qt_targets)
-- 
cgit v1.2.3