173099696f
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
25 lines
549 B
Prolog
25 lines
549 B
Prolog
load(qttest_p4)
|
|
SOURCES += tst_qdir.cpp
|
|
RESOURCES += qdir.qrc
|
|
QT = core
|
|
|
|
wince*|symbian {
|
|
DirFiles.files = testdir testData searchdir resources entrylist types tst_qdir.cpp
|
|
DirFiles.path = .
|
|
DEPLOYMENT += DirFiles
|
|
}
|
|
|
|
wince* {
|
|
DEFINES += SRCDIR=\\\"\\\"
|
|
} else:symbian {
|
|
TARGET.CAPABILITY += AllFiles
|
|
TARGET.UID3 = 0xE0340002
|
|
DEFINES += SYMBIAN_SRCDIR_UID=$$lower($$replace(TARGET.UID3,"0x",""))
|
|
LIBS += -lefsrv
|
|
INCLUDEPATH += $$MW_LAYER_SYSTEMINCLUDE
|
|
} else {
|
|
DEFINES += SRCDIR=\\\"$$PWD/\\\"
|
|
}
|
|
|
|
CONFIG += parallel_test
|