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
30 lines
689 B
Prolog
30 lines
689 B
Prolog
load(qttest_p4)
|
|
SOURCES += tst_qdatastream.cpp
|
|
|
|
!symbian: {
|
|
cross_compile: DEFINES += SVGFILE=\\\"tests2.svg\\\"
|
|
else: DEFINES += SVGFILE=\\\"gearflowers.svg\\\"
|
|
}
|
|
|
|
# for qpaintdevicemetrics.h
|
|
QT += svg
|
|
|
|
|
|
wince*: {
|
|
addFiles.files = datastream.q42 tests2.svg
|
|
addFiles.path = .
|
|
DEPLOYMENT += addFiles
|
|
DEFINES += SRCDIR=\\\"\\\"
|
|
} else:symbian {
|
|
# SRCDIR and SVGFILE defined in code in symbian
|
|
addFiles.files = datastream.q42 tests2.svg
|
|
addFiles.path = .
|
|
DEPLOYMENT += addFiles
|
|
TARGET.EPOCHEAPSIZE = 1000000 10000000
|
|
TARGET.UID3 = 0xE0340001
|
|
DEFINES += SYMBIAN_SRCDIR_UID=$$lower($$replace(TARGET.UID3,"0x",""))
|
|
}else {
|
|
DEFINES += SRCDIR=\\\"$$PWD/\\\"
|
|
}
|
|
|