76f6ceec36
Testcases and benchmarks are rather different entities. You won't usually want to run benchmarks in the same environment you are wanting to run tests in, so this feature allows to differentiate between the two. We also add a "benchmark" make target (similar to check), which runs all configured benchmarks. Change-Id: I33759ce44c34e42a6a3a88f34e7b9c4372380721 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@theqtcompany.com>
20 lines
556 B
Plaintext
20 lines
556 B
Plaintext
|
|
# Let every project have a standard GNU `check' target
|
|
!contains(QMAKE_EXTRA_TARGETS, check) {
|
|
contains(TEMPLATE, subdirs): \
|
|
prepareRecursiveTarget(check)
|
|
else: \
|
|
check.depends = first # `make check' implies build
|
|
QMAKE_EXTRA_TARGETS += check
|
|
}
|
|
|
|
# ... and the same for benchmarks, too.
|
|
!contains(QMAKE_EXTRA_TARGETS, benchmark) {
|
|
contains(TEMPLATE, subdirs): \
|
|
prepareRecursiveTarget(benchmark)
|
|
else: \
|
|
benchmark.depends = first # `make benchmark' implies build
|
|
QMAKE_EXTRA_TARGETS += benchmark
|
|
}
|
|
|