summaryrefslogtreecommitdiffstats
path: root/demos
diff options
context:
space:
mode:
authorAnders Bakken <anders.bakken@nokia.com>2009-09-11 15:04:07 (GMT)
committerAnders Bakken <anders.bakken@nokia.com>2009-09-11 15:42:30 (GMT)
commitbd513e9feeb70068d4d638f1a72843be195a924d (patch)
treedeb16744816ffa7eefc67b8cf167f7d1a94cfefa /demos
parent3fed939e82e4946546775602f4898c363871c3f2 (diff)
downloadQt-bd513e9feeb70068d4d638f1a72843be195a924d.zip
Qt-bd513e9feeb70068d4d638f1a72843be195a924d.tar.gz
Qt-bd513e9feeb70068d4d638f1a72843be195a924d.tar.bz2
Don't use UI_TOOLS for browser demo on QWS
When cross-compiling and shadow building Makefiles are not generated for designer and libQtUiTools. For this reason designer usually doesn't build for people trying to compile the browser example on QWS due to unresolved externals or weird link errors when the build tries to pick up the system Qt libraries instead. The mechanism to fix this is already in place for S60.
Diffstat (limited to 'demos')
-rw-r--r--demos/browser/browser.pro2
1 files changed, 1 insertions, 1 deletions
diff --git a/demos/browser/browser.pro b/demos/browser/browser.pro
index f54afe4..afc25e3 100644
--- a/demos/browser/browser.pro
+++ b/demos/browser/browser.pro
@@ -3,7 +3,7 @@ TARGET = browser
QT += webkit network
CONFIG += qt warn_on
-contains(QT_BUILD_PARTS, tools):!symbian: CONFIG += uitools
+contains(QT_BUILD_PARTS, tools):!symbian:!embedded: CONFIG += uitools
else: DEFINES += QT_NO_UITOOLS
FORMS += \