qt5base-lts/tests/auto/qlocalsocket/lackey/lackey.pro

#include(../src/src.pri)

QT = core script network

requires(contains(QT_CONFIG,script))

CONFIG += qtestlib

DESTDIR = ./

win32: CONFIG += console
mac:CONFIG -= app_bundle

DEFINES += QLOCALSERVER_DEBUG
DEFINES += QLOCALSOCKET_DEBUG

SOURCES		+= main.cpp
TARGET		= lackey

symbian:TARGET.CAPABILITY = ALL -TCB
Initial import from the monolithic Qt. This is the beginning of revision history for this module. If you want to look at revision history older than this, please refer to the Qt Git wiki for how to use Git history grafting. At the time of writing, this wiki is located here: http://qt.gitorious.org/qt/pages/GitIntroductionWithQt If you have already performed the grafting and you don't see any history beyond this commit, try running "git log" with the "--follow" argument. Branched from the monolithic repo, Qt master branch, at commit 896db169ea224deb96c59ce8af800d019de63f12 2011-04-27 10:05:43 +00:00			`#include(../src/src.pri)`

			`QT = core script network`

			`requires(contains(QT_CONFIG,script))`

			`CONFIG += qtestlib`

			`DESTDIR = ./`

			`win32: CONFIG += console`
			`mac:CONFIG -= app_bundle`

			`DEFINES += QLOCALSERVER_DEBUG`
			`DEFINES += QLOCALSOCKET_DEBUG`

			`SOURCES += main.cpp`
			`TARGET = lackey`

tests: clean up usage of QT_CONFIG to fix circular dependencies With modularized Qt, using QT_CONFIG is dangerous, because the behavior changes depending on the order in which modules are qmake'd. For example, an autotest doing: contains(QT_CONFIG,svg):QT += svg ...will depend on libQtSvg if (and only if) the autotest is qmake'd _after_ qtsvg is qmake'd. This makes the tested functionality unpredictable. Also, if the above example occurs within qtbase, it causes the test to sometimes have a circular dependency: if qtsvg is qmake'd before the test is qmake'd, the test in qtbase depends on qtsvg which depends on qtbase. Tests must avoid functionality tests via QT_CONFIG except where all the tested modules are dependencies of the current module. Usage of QT_CONFIG with qt3support was entirely removed since Qt5 will not retain qt3support. Reviewed-by: Jason McDonald Change-Id: I5a5013b3ec7e1f38fb78864763c9e7586c15e70b 2011-05-16 00:43:14 +00:00			`symbian:TARGET.CAPABILITY = ALL -TCB`