blocks|key|2273919|text|在Qt+4.8中，这变得非常容易。所有必需的库现在都是Qt本身的一部分，您不必自己为Qt版本构建调试库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2273920|我正在开发一个Qt/QML桌面应用程序，它也是用CMake构建的。我必须完成以下步骤才能启用QML调试：|2273921|将调试支持器包括到应用程序的启动代码中。
#包括+/*+.+*/+QDeclarativeDebuggingEnabler使能器；|ordered-list-item|2273922|将QML_DISABLE_OPTIMIZER=1添加到应用程序的执行环境中
这可以在项目页的“执行”选项卡的Qt中完成。|offset|length|style|CODE|2273923|勾选“执行”选项卡中的QML调试复选框。
这为Qt和嵌入在应用程序中的QML调试器组件之间的通信添加了所需的命令行参数。|2273924|如果一切顺利，如果在调试模式下启动，应用程序将使用以下输出向您致意：|2273925|启用了Qml调试。只在安全的环境中使用！
QDeclarativeDebugServer:在3768端口等待连接.
QDeclarativeDebugServer:建立连接|blockquote|2273926|之后，我能够设置断点并检查变量。另外，通过分析页面访问的分析器也起了作用。|2273927|您的情况显然要复杂一些，因为您正在开发一个嵌入式应用程序。|2273928|Qt创建者不支持在嵌入式平台上部署和执行基于CMake的项目。你必须自己去做。不要忘记将所需的参数传递给应用程序以配置QML调试：|2273929|$+your-app+-qmljsdebugger=port:3768,block|code-block|syntax|javascript|2273930|要将Qt附加到远程运行的应用程序进行分析会话，请使用Qt主菜单中的“分析”菜单中相应的“外部”条目。在"Debug“>+"Debug”下使用"Connect+to+Debug-Server“进行调试也有类似的选项。|2273931|entityMap^0|0|0|0|1|N|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1A|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|1B|8|@$I|1C|J|1D|K|L]]|9|@]|A|$]]|$1|M|3|N|5|F|7|1E|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|1G|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1H|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1I|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1J|8|@]|9|@]|A|$]]|$1|Z|3|10|5|11|7|1K|8|@]|9|@]|A|$12|13]]|$1|14|3|15|5|6|7|1L|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|17|$]]

With Qt 4.8 this got pretty easy. All required libraries are now part of Qt itself and you don't have to build the debug library for your Qt version yourself.

I'm developing a Qt/QML desktop application also built with CMake. I had to complete the following steps to enable QML debugging:

<ol>
<li>Include the debugging enabler into my application's start-up code

<pre><code> #include &lt;QtDeclarative/qdeclarativedebug.h&gt;

 /* [...] */

 QDeclarativeDebuggingEnabler enabler;
</code></pre></li>
<li>Add <code>QML_DISABLE_OPTIMIZER=1</code> to execution environment of my application

This can be done within Qt Creator in the execution tab of the projects page.</li>
<li>Tick the checkbox for QML debugging also found in the execution tab

This adds the required command line parameters for the communication between Qt Creator and the QML debugger component embedded in the application</li>
</ol>

If everything went fine the application greets you with the following output if started in debug mode:

<blockquote>
 Qml debugging is enabled. Only use this in a safe environment! 
 QDeclarativeDebugServer: Waiting for connection on port 3768... 
 QDeclarativeDebugServer: Connection established
</blockquote>

After that I was able to set breakpoints and inspect variables. Also the profiler accessible via the analyze page just worked.

Your case is obviously a little bit more complicated as your developing an embedded application.

Qt creator has no support for deploying and executing CMake-based projects on embedded platforms. You will have to do that yourself. Don't forget to pass the required arguments to your application to configure the QML debugging:

<pre><code>$ your-app -qmljsdebugger=port:3768,block
</code></pre>

To attach Qt Creator to a remotely running application for a profiling session use the corresponding "External" entries in the "Analyze" menu in the Qt Creator main menu. Where is a likewise option for debugging with "Connect to Debug-Server" under "Debug" > "Debug".

blocks|key|1130147|text|这里是@sebasgo的答案的一个“更清洁”的替代方案，第1项。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1130148|如果您将Qt5与QtQuick2结合使用，则只需在某个文件中包含QtQuick之前定义QT_QML_DEBUG+(只要它是可执行文件的一部分，不管是哪个文件)。例如，用行启动main.cpp就足够了：|style|CODE|1130149|#define+QT_QML_DEBUG
#include+<QtQuick>|code-block|syntax|javascript|1130150|如果您只在调试版本中使用编译器的-DQT_QML_DEBUG标志(例如通过qmake+定义或cmake+定义指令)，这不会有什么影响。|1130151|如果您被遗留的QtQuick1所困(无论是在Qt5还是Qt4中)，请使用QT_DECLARATIVE_DEBUG宏。|1130152|#define+QT_DECLARATIVE_DEBUG
#include+<QtDeclarative>|1130153|对于好奇的人来说，这里有一个相关的Qt源代码，简短且不言自明：|1130154|QtQuick2|unordered-list-item|1130155|QtQuick1+in+Qt5|1130156|QtQuick1+(+Qt4.8+)|1130157|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/13366495/how-to-qt-qml-debugging-and-or-profiling#13440000|1|http://qt-project.org/doc/qt-5.0/qtdoc/qmake-variable-reference.html#defines|2|http://www.cmake.org/cmake/help/v2.8.11/cmake.html#command:add_definitions|3|http://qt.gitorious.org/qt/qtdeclarative/blobs/stable/src/qml/debugger/qqmldebug.h|4|http://qt.gitorious.org/qt/qtquick1/blobs/stable/src/declarative/debugger/qdeclarativedebug.h|5|http://qt.gitorious.org/qt/qt/blobs/4.8/src/declarative/debugger/qdeclarativedebug.h^0|3|B|0|0|W|7|17|C|2F|8|0|0|G|E|17|2|1|1G|2|2|0|10|K|0|0|0|0|8|3|0|0|F|4|0|0|I|5|0^^$0|@$1|2|3|4|5|6|7|1J|8|@]|9|@$A|1K|B|1L|1|1M]]|C|$]]|$1|D|3|E|5|6|7|1N|8|@$A|1O|B|1P|F|G]|$A|1Q|B|1R|F|G]|$A|1S|B|1T|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|1U|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1V|8|@$A|1W|B|1X|F|G]]|9|@$A|1Y|B|1Z|1|20]|$A|21|B|22|1|23]]|C|$]]|$1|O|3|P|5|6|7|24|8|@$A|25|B|26|F|G]]|9|@]|C|$]]|$1|Q|3|R|5|J|7|27|8|@]|9|@]|C|$K|L]]|$1|S|3|T|5|6|7|28|8|@]|9|@]|C|$]]|$1|U|3|V|5|W|7|29|8|@]|9|@$A|2A|B|2B|1|2C]]|C|$]]|$1|X|3|Y|5|W|7|2D|8|@]|9|@$A|2E|B|2F|1|2G]]|C|$]]|$1|Z|3|10|5|W|7|2H|8|@]|9|@$A|2I|B|2J|1|2K]]|C|$]]|$1|11|3|-4|5|6|7|2L|8|@]|9|@]|C|$]]]|12|$13|$5|14|15|16|C|$17|18]]|19|$5|14|15|16|C|$17|1A]]|1B|$5|14|15|16|C|$17|1C]]|1D|$5|14|15|16|C|$17|1E]]|1F|$5|14|15|16|C|$17|1G]]|1H|$5|14|15|16|C|$17|1I]]]]

Here is a "cleaner" alternative to <a href="https://stackoverflow.com/questions/13366495/how-to-qt-qml-debugging-and-or-profiling#13440000">@sebasgo's answer</a>, item 1.

If you are using Qt5 with QtQuick2, you only need to define <code>QT_QML_DEBUG</code> before including <code>QtQuick</code> in some file (it does not matter what file, as long as it is a part of the executable). For example, it is sufficient to start your <code>main.cpp</code> with lines:

<pre><code>#define QT_QML_DEBUG
#include &lt;QtQuick&gt;
</code></pre>

It won't hurt if you instead use compiler's <code>-DQT_QML_DEBUG</code> flag (e.g. via qmake <a href="http://qt-project.org/doc/qt-5.0/qtdoc/qmake-variable-reference.html#defines" rel="nofollow noreferrer">DEFINES</a> or cmake <a href="http://www.cmake.org/cmake/help/v2.8.11/cmake.html#command:add_definitions" rel="nofollow noreferrer">add_definitions</a> directives), possibly only in debug builds.

If you are stuck with legacy QtQuick1 (in either Qt5 or Qt4) use <code>QT_DECLARATIVE_DEBUG</code> macro instead, e.g.

<pre><code>#define QT_DECLARATIVE_DEBUG
#include &lt;QtDeclarative&gt;
</code></pre>

For the curious, here is a relevant Qt source, short and self-explanatory:

<ul>
<li><a href="http://qt.gitorious.org/qt/qtdeclarative/blobs/stable/src/qml/debugger/qqmldebug.h" rel="nofollow noreferrer">QtQuick2</a></li>
<li><a href="http://qt.gitorious.org/qt/qtquick1/blobs/stable/src/declarative/debugger/qdeclarativedebug.h" rel="nofollow noreferrer">QtQuick1 in Qt5</a></li>
<li><a href="http://qt.gitorious.org/qt/qt/blobs/4.8/src/declarative/debugger/qdeclarativedebug.h" rel="nofollow noreferrer">QtQuick1 in Qt4.8</a></li>
</ul>

blocks|key|1795136|text|在QT5.1中，添加了新的函数qInstallMessageHandler。它将允许您捕获并记录错误和警告，这样您就可以随意处理它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1795137|entityMap|0|LINK|mutability|MUTABLE|url|http://qt-project.org/doc/qt-5.0/qtcore/qtglobal.html#qInstallMessageHandler^0|F|M|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

With Qt 5.1 the new function <a href="http://qt-project.org/doc/qt-5.0/qtcore/qtglobal.html#qInstallMessageHandler" rel="nofollow">qInstallMessageHandler</a> was added.
It will let you catch, and log, errors and warnings so you can deal with them as you like.

blocks|key|1795163|text|我用的是Qt+5，它变得更容易了。我只需要这一步就可以进行QML分析：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1795164|#include+<QQmlDebuggingEnabler>

...

QQmlDebuggingEnabler+enabler;|code-block|syntax|javascript|1795165|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I'm using Qt 5, and it got even easier. Just this one step was required on my side to do QML profiling:

<pre><code>#include &lt;QQmlDebuggingEnabler&gt;

...

QQmlDebuggingEnabler enabler;
</code></pre>

blocks|key|1795193|text|检查文档所有给出的答案似乎是不必要的。此外，它在版本中硬编码调试代码。我不知道为什么需要QQmlDebuggingEnabler，但是如果您检查代码这里和这里，您就会发现，不需要安装QQmlDebuggingEnabler。只需包含QQmlDebuggingEnabler并设置QT_QML_DEBUG标志，例如，如下(CMake)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1795194|set(CMAKE_CXX_FLAGS_DEBUG+"${CMAKE_CXX_FLAGS_DEBUG}+-DQT_QML_DEBUG+")|1795195|然而，根据文档的说法，QQmlDebuggingEnabler是不必要的。|1795196|此外:分析未优化的代码是没有意义的。|1795197|对我来说，将QT_QML_DEBUG设置为标志并检查QML调试的复选框就足够了。|1795198|entityMap|0|LINK|mutability|MUTABLE|url|http://doc.qt.io/qtcreator/creator-debugging.html|1|https://github.com/cedrus/qt/blob/master/qtdeclarative/include/QtQml/QQmlDebuggingEnabler|2|https://github.com/cedrus/qt/blob/master/qtdeclarative/src/qml/debugger/qqmldebug.h|3^0|18|K|2J|K|38|K|3V|C|2|2|0|22|2|1|25|2|2|0|0|1X|0|B|K|5|2|3|0|0|6|C|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]|$9|15|A|16|B|C]|$9|17|A|18|B|C]]|D|@$9|19|A|1A|1|1B]|$9|1C|A|1D|1|1E]|$9|1F|A|1G|1|1H]]|E|$]]|$1|F|3|G|5|6|7|1I|8|@$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1L|8|@$9|1M|A|1N|B|C]]|D|@$9|1O|A|1P|1|1Q]]|E|$]]|$1|J|3|K|5|6|7|1R|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1S|8|@$9|1T|A|1U|B|C]]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1V|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U]]|V|$5|Q|R|S|E|$T|W]]|X|$5|Q|R|S|E|$T|Y]]|Z|$5|Q|R|S|E|$T|U]]]]

Checking the <a href="http://doc.qt.io/qtcreator/creator-debugging.html" rel="nofollow">docs</a> all given answers seem to be unnecessary. Further it hardcodes debug code in releases. I have no clue why <code>QQmlDebuggingEnabler</code> would be necessary, but if you check the code <a href="https://github.com/cedrus/qt/blob/master/qtdeclarative/include/QtQml/QQmlDebuggingEnabler" rel="nofollow">here</a> and <a href="https://github.com/cedrus/qt/blob/master/qtdeclarative/src/qml/debugger/qqmldebug.h" rel="nofollow">here</a>, you will recognize, that the instatiation of <code>QQmlDebuggingEnabler</code> is not necessary. Just include <code>QQmlDebuggingEnabler</code> and set the <code>QT_QML_DEBUG</code> flag e.g. like this (CMake)

<code>set(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_CXX_FLAGS_DEBUG} -DQT_QML_DEBUG ")</code>

However according to the <a href="http://doc.qt.io/qtcreator/creator-debugging.html" rel="nofollow">docs</a> <code>QQmlDebuggingEnabler</code> is not necessary.

Furtermore: profiling unoptimized code makes no sense.

For me setting <code>QT_QML_DEBUG</code> as flag and checking the checkbox for QML debugging is sufficient.

What software Qt/QML pieces are needed to compile in an app to be able to debug/profile QML?

My current app is build using cmake and runs on a embedded device. Furthermore, I'm starting to use Qt 4.8.3 (until now 4.7.0).

I would like to use these fancy/cool features (for an embedded developer):

<a href="http://doc.qt.digia.com/qtcreator/creator-qml-performance-monitor.html" rel="noreferrer">http://doc.qt.digia.com/qtcreator/creator-qml-performance-monitor.html</a>

I've searched trough <a href="http://qt-project.org" rel="noreferrer">qt-project</a> looking for help, but I haven't got clear what are the steps needed when you want to debug/profile a remote app, with a customize build environment.

So, I would like to know if it is needed any of the following steps, and in positive case, what is in fact the needed code.

<ul>
<li>Qt libraries ./configure specific options.</li>
<li>QtCreator specific options to attach/launch to remote app.</li>
<li>Cmake includes and libraries needed in the final app executable .</li>
</ul>

Any help, link, etc is welcomed.

How to Qt - Qml debugging and/or profiling?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

要在应用程序中编译哪些软件Qt/QML才能调试/配置QML？我现在的应用程序是使用cmake构建的，运行在嵌入式设备上。此外，我开始使用QT4.8.3(到目前为止是4.7.0)。我想使用这些花哨的/很酷的特性(对于嵌入式开发人员)：我已经在中搜索帮助，但我还不清楚当您想要调试/配置远程应用程序时，需要使用自定义构建环境...

问如何进行Qml调试和/或分析？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何进行Qml调试和/或分析？EN