Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-94581 Review and Document new Qt 6.2 CMake API
  3. QTBUG-95140

Revise what should be the default target and output name of a qml plugin

    XMLWordPrintable

Details

    • a25f650c317e4886007a8beb0e9f2f7e973e6e7c (qt/qtdeclarative/dev) 96fdbf597e581fe5e09e02758a4a2b0fe12add53 (qt/qtdeclarative/6.2)

    Description

      Context
      https://git.qt.io/alcroito/qt6-cmake-api-review/-/commit/14b4999bc857f5402a3577fe334ebfb3602ad0c2#f3ff9c1b48af14adf093e2af0c5cf2849829bb6d_24_24

      The proposal is to change the output name of the plugin to lower case and append '_plugin', and see what breaks.
      Check what actual name we write out into the qmldir file.

      Open question left is whether the default target name should be renamed to lower case as well.

      One point is that we might want to be consistent in naming all our plugin targets to end with Plugin suffix, like we do for regular qt plugins.
      But it's not strictly necessary for qml plugins, because our current restriction of globbing plugin Config files ending with Plugin is only there for qt plugins, not qml plugins.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              crscott Craig Scott
              alexandru.croitor Alexandru Croitor
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: