summaryrefslogtreecommitdiffstats
path: root/tests/benchmarks/corelib/kernel/qmetaobject/qmetaobject.pro
diff options
context:
space:
mode:
authorEdward Welbourne <edward.welbourne@qt.io>2020-03-30 16:15:44 +0200
committerEdward Welbourne <edward.welbourne@qt.io>2020-04-02 18:33:42 +0200
commit53ed635dbb5d1ab8103eb1161f81c7e4102d1df2 (patch)
tree5e79eecd6a39abf6eb052a4104ed8af434a121a5 /tests/benchmarks/corelib/kernel/qmetaobject/qmetaobject.pro
parent1430b2944b243b387c9f311c061a5caaf16edea6 (diff)
Set CONFIG += benchmark in corelib's various benchmarks
This leads to "make benchmark" actually running the benchmark, which would be nice, I think. Purged various CONFIG += release or -= debug lines from the same configurations; those surely only configure how the test code is compiled, which is more or less pointless; it's the code under test whose debug/release state matters, and I don't suppose that's affected by the build config of the test code. In the process, reduce diversity of the ordering of lines within these *.pro files and purge some dangling space. Change-Id: Ia9f9f0ca4c096262de928806bdfa6ea3b9e7b9ba Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
Diffstat (limited to 'tests/benchmarks/corelib/kernel/qmetaobject/qmetaobject.pro')
-rw-r--r--tests/benchmarks/corelib/kernel/qmetaobject/qmetaobject.pro3
1 files changed, 2 insertions, 1 deletions
diff --git a/tests/benchmarks/corelib/kernel/qmetaobject/qmetaobject.pro b/tests/benchmarks/corelib/kernel/qmetaobject/qmetaobject.pro
index 47d2acb9b1..0d595ed4da 100644
--- a/tests/benchmarks/corelib/kernel/qmetaobject/qmetaobject.pro
+++ b/tests/benchmarks/corelib/kernel/qmetaobject/qmetaobject.pro
@@ -1,5 +1,6 @@
TEMPLATE = app
+CONFIG += benchmark
QT += widgets testlib
-TARGET = tst_bench_qmetaobject
+TARGET = tst_bench_qmetaobject
SOURCES += main.cpp