Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. Qt Creator: How to explicitly run qmllint?
Qt 6.12 LTS is out! See what's new in the release blog

Qt Creator: How to explicitly run qmllint?

Scheduled Pinned Locked Moved Unsolved Qt Creator and other tools
5 Posts 3 Posters 2.2k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    Asperamanca
    wrote on last edited by
    #1

    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?

    S 1 Reply Last reply
    1
    • A Asperamanca

      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?

      S Offline
      S Offline
      schneid361
      wrote on last edited by
      #2

      @Asperamanca Hi, did you ever figure this out?

      1 Reply Last reply
      0
      • SGaistS Offline
        SGaistS Offline
        SGaist
        Lifetime Qt Champion
        wrote on last edited by aha_1980
        #3

        Hi,

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

        [Edit aha_1980: Fixed typo]

        Interested in AI ? www.idiap.ch
        Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

        A 1 Reply Last reply
        2
        • SGaistS SGaist

          Hi,

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

          [Edit aha_1980: Fixed typo]

          A Offline
          A Offline
          Asperamanca
          wrote on last edited by
          #4

          @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.

          SGaistS 1 Reply Last reply
          0
          • A Asperamanca

            @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.

            SGaistS Offline
            SGaistS Offline
            SGaist
            Lifetime Qt Champion
            wrote on last edited by
            #5

            @Asperamanca isn't that the role of the additional generated targets ? You can invoke them directly.

            Interested in AI ? www.idiap.ch
            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

            1 Reply Last reply
            0

            • Login

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Users
            • Groups
            • Search
            • Get Qt
            • Unsolved