diff options
author | Edward Welbourne <edward.welbourne@qt.io> | 2020-03-30 16:15:44 +0200 |
---|---|---|
committer | Edward Welbourne <edward.welbourne@qt.io> | 2020-04-02 18:33:42 +0200 |
commit | 53ed635dbb5d1ab8103eb1161f81c7e4102d1df2 (patch) | |
tree | 5e79eecd6a39abf6eb052a4104ed8af434a121a5 /tests/benchmarks/corelib/kernel/qvariant | |
parent | 1430b2944b243b387c9f311c061a5caaf16edea6 (diff) | |
download | qtbase-53ed635dbb5d1ab8103eb1161f81c7e4102d1df2.tar.gz |
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/qvariant')
-rw-r--r-- | tests/benchmarks/corelib/kernel/qvariant/qvariant.pro | 7 |
1 files changed, 2 insertions, 5 deletions
diff --git a/tests/benchmarks/corelib/kernel/qvariant/qvariant.pro b/tests/benchmarks/corelib/kernel/qvariant/qvariant.pro index 8a8e9f25d3..2616ae78ea 100644 --- a/tests/benchmarks/corelib/kernel/qvariant/qvariant.pro +++ b/tests/benchmarks/corelib/kernel/qvariant/qvariant.pro @@ -1,9 +1,6 @@ -TARGET = tst_bench_qvariant +CONFIG += benchmark QT += testlib !qtHaveModule(gui): QT -= gui -CONFIG += release -#CONFIG += debug - - +TARGET = tst_bench_qvariant SOURCES += tst_qvariant.cpp |