a170c974a5
We should not check for platforms, but rather for features. Also, if dbus is available it doesn't automatically mean that QProcess is. Change-Id: I27ef5863fcb107cca1aa47abba95b734962adc33 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>
37 lines
930 B
Prolog
37 lines
930 B
Prolog
TEMPLATE=subdirs
|
|
|
|
# Run this test first
|
|
SUBDIRS=\
|
|
qdbusconnection_delayed
|
|
|
|
SUBDIRS+=\
|
|
qdbusabstractadaptor \
|
|
qdbusabstractinterface \
|
|
qdbusconnection \
|
|
qdbusconnection_no_app \
|
|
qdbusconnection_no_bus \
|
|
qdbusconnection_no_libdbus \
|
|
qdbusconnection_spyhook \
|
|
qdbuscontext \
|
|
qdbusinterface \
|
|
qdbuslocalcalls \
|
|
qdbusmarshall \
|
|
qdbusmetaobject \
|
|
qdbusmetatype \
|
|
qdbuspendingcall \
|
|
qdbuspendingreply \
|
|
qdbusreply \
|
|
qdbusservicewatcher \
|
|
qdbustype \
|
|
qdbusthreading \
|
|
qdbusxmlparser
|
|
|
|
!qtConfig(private_tests): SUBDIRS -= \
|
|
qdbusmarshall \
|
|
|
|
!qtConfig(process): SUBDIRS -= \
|
|
qdbusabstractadaptor \
|
|
qdbusabstractinterface \
|
|
qdbusinterface \
|
|
qdbusmarshall
|