Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-93625

qt_internal_add_test doesn't call qt_import_qml_plugins

    XMLWordPrintable

Details

    • df040fb11 (dev), 412e08106 (dev), a72dacce2 (dev), 2bbc0bda3 (dev), 45c8ab114 (6.8), 25f575e85 (dev), 79507816f (6.8), e4549375c (6.8), c53a9d9ff (6.8), feaeb68a2 (6.8), d5c5e8380 (dev), 8c91757e9 (dev), 19702c9bc (6.8), 17856391a (6.8)

    Description

      Currently tests created by qt_internal_add_test don't have qmlimportscanner run for them (via qt_import_qml_plugins).
      This means that in a static Qt build, if the test needs some qml plugins, the test will fail at runtime saying some qml import has failed.

      In examples added by the public qt_add_executable, we run qt_import_qml_plugins via scope finalizers.

      For tests we have a few options:

      • call qt_import_qml_plugins directly in qt_internal_add_test()
      • Call it via scope finalizer (only this one function)
      • Call all scope finalizers like we do in qt_add_executable. This might prove problematic to implement.

      We can't call qt_import_qml_plugins when building the qtdeclarative tests as part of the overall qtdeclarative build (or a top-level build), but we can do it for standalone test builds, which is what is used by the CI.

      Attachments

        Issue Links

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

          Activity