<![CDATA[Qt Creator: How to explicitly run qmllint?]]>I have a cmake project with integrated qmllint. That means, if I e.g. rebuild, I will get all qmllint warnings.

How can I run qmllint explicitly if I do not want to rebuild, but only see any remaining qmllint warnings?

]]>https://forum.qt.io/topic/146064/qt-creator-how-to-explicitly-run-qmllintRSS for NodeSat, 31 Oct 2026 08:34:46 GMTWed, 28 Jun 2023 07:18:40 GMT60<![CDATA[Reply to Qt Creator: How to explicitly run qmllint? on Tue, 09 Jan 2024 19:53:39 GMT]]>@Asperamanca isn't that the role of the additional generated targets ? You can invoke them directly.

]]>https://forum.qt.io/post/785801https://forum.qt.io/post/785801Tue, 09 Jan 2024 19:53:39 GMT<![CDATA[Reply to Qt Creator: How to explicitly run qmllint? on Tue, 09 Jan 2024 14:36:08 GMT]]>@SGaist Actually, while my questions was specifically targeted at qmllint (and your answer for that is correct), what I actually meant were all QML related warnings. They come from different tools (e.g. qmllint, but also qmlsc). So getting all the QML-related warnings without a rebuild is actually quite complicated: You have to delete the corresponding generated QML module files in the build folder to force re-generating them.

]]>https://forum.qt.io/post/785777https://forum.qt.io/post/785777Tue, 09 Jan 2024 14:36:08 GMT<![CDATA[Reply to Qt Creator: How to explicitly run qmllint? on Sun, 24 Dec 2023 04:28:57 GMT]]>Hi,

Based one the qt_add_qml_module documentation, linting targets are created that you can call.

[Edit aha_1980: Fixed typo]

]]>https://forum.qt.io/post/783807https://forum.qt.io/post/783807Sun, 24 Dec 2023 04:28:57 GMT<![CDATA[Reply to Qt Creator: How to explicitly run qmllint? on Wed, 20 Dec 2023 19:08:39 GMT]]>@Asperamanca Hi, did you ever figure this out?

]]>https://forum.qt.io/post/783803https://forum.qt.io/post/783803Wed, 20 Dec 2023 19:08:39 GMT