Why?

Cause

• As a developer I want my QML types resolved. Now when the QML type is derived from an external module other than installed ones this does not work.
• This can be fixed by finding a proper way of resolving QML imports and adding them to the qmldom arguments where it's being invoked from androiddeployqt.
   (see QTBUG-127554)

Customer

• Android Developer using QtDS and AS

Cruft

• Also generic and not only QtDS 

What?

Definition

• Improve qmldir path discovery in ADQt code generator by finding a proper way of resolving QML imports and adding them to the qmldom arguments where it's being invoked from androiddeployqt
• The attached project does not work out of the box because if several reasons including above:

1. 1. The App/main.cpp handles QQuickView creation which conflicts with QtQuickView
   2. The QtDSProjectContent/App.qml as the component which is going to be loaded by QtQuickView (currently loaded in main.cpp as an input tho QQmlApplicationEngine) already has a Window root. This is not allowed by QtQuickView because it expects to instantiate QQuickView as the main window.
   3. Raised by this issuse: even if we fix the QtDS project with the above, building the project will fail if QT_ANDROID_GENERATE_JAVA_QTQUICKVIEW_CONTENTS is provided to be ON as a cmake variable.
      QtDSProject.tar.gz

Demarcation

• Design Studio changes not needed

Dependencies

• FF due to androiddeployqt changes
• QTBUG-125891 ?