Edward Welbourne 53ed635dbb 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>		2020-04-02 18:33:42 +02:00
..
events	Set CONFIG += benchmark in corelib's various benchmarks	2020-04-02 18:33:42 +02:00
qcoreapplication	Set CONFIG += benchmark in corelib's various benchmarks	2020-04-02 18:33:42 +02:00
qmetaobject	Set CONFIG += benchmark in corelib's various benchmarks	2020-04-02 18:33:42 +02:00
qmetatype	Set CONFIG += benchmark in corelib's various benchmarks	2020-04-02 18:33:42 +02:00
qobject	Set CONFIG += benchmark in corelib's various benchmarks	2020-04-02 18:33:42 +02:00
qtimer_vs_qmetaobject	Set CONFIG += benchmark in corelib's various benchmarks	2020-04-02 18:33:42 +02:00
qvariant	Set CONFIG += benchmark in corelib's various benchmarks	2020-04-02 18:33:42 +02:00
kernel.pro	Enable and extend the qtimer_vs_qmetaobject benchmark	2019-03-27 06:37:33 +00:00