aboutsummaryrefslogtreecommitdiffstats
path: root/src/qml/qml.pro
diff options
context:
space:
mode:
authorMilian Wolff <milian.wolff@kdab.com>2019-04-29 10:46:02 +0200
committerMilian Wolff <milian.wolff@kdab.com>2019-05-05 21:23:36 +0000
commitd2c089eb11d3ad6a9917efde8f13b36931b35baf (patch)
treeda5df88a71f3e7c3479d6cb6682a528d8cc640aa /src/qml/qml.pro
parent006f8b666f90b356976c9948a8a79b722b38c9b1 (diff)
Add Q_TRACE calls to QtQml for QML profiler trace points
This adds tracepoints for LTTng/ETW at the positions that are also used by the QML profiler within QtQml. I.e. with the tracepoints here, you'll see which QML function is being executed which is already quite helpful. This will allow us to bridge the gap between C++ and QML when tracing with LTTng/ETW. Additionally, you'll also be able to see kernel tracepoints which bridges another gap. Combined, this approach can give much deeper insights into what the (embedded) system is doing compared to just looking at the QML profiler alone. Change-Id: Ia8f71bf6d44b7f51c3c5aaa38f032675604aeca6 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> Reviewed-by: Rafael Roquetto <rafael@roquetto.com>
Diffstat (limited to 'src/qml/qml.pro')
-rw-r--r--src/qml/qml.pro3
1 files changed, 3 insertions, 0 deletions
diff --git a/src/qml/qml.pro b/src/qml/qml.pro
index db59140f06..d2170ac40b 100644
--- a/src/qml/qml.pro
+++ b/src/qml/qml.pro
@@ -4,6 +4,9 @@ QT = core-private
qtConfig(qml-network): \
QT += network
+TRACEPOINT_PROVIDER = $$PWD/qtqml.tracepoints
+CONFIG += qt_tracepoints
+
DEFINES += QT_NO_URL_CAST_FROM_STRING QT_NO_INTEGER_EVENT_COORDINATES
msvc:equals(QT_ARCH, i386): QMAKE_LFLAGS += /BASE:0x66000000