When the QML files are all bundled into a .qrc file, they don't get
copied to the install dir, which would lead to qmlimportscanner not picking
up the dependencies (e.g. QtQuick Controls) for android packaging.
Looking at commit 1b0496d, I wonder if maybe we should be able to specify
two paths to look into? But qmlimportscanner doesn't support that, does it?
using this toolchain for a basic QtQuick2 app created from a
QtCreator template, with Qt Quick Controls support, and QML files
in a Qt resource.
| Automatic diff as part of commit; lint not applicable. |
| Automatic diff as part of commit; unit tests not applicable. |
This will be problematic as soon as your application depends on any libraries.
So far we've worked with the assumption that you'd install the applications into a prefix then ran androiddeployqt over this file.
You mean, libraries which themselves have installed QML files, right? Depending on e.g. ki18n is no problem.
But yeah I can see how this would be a problem for something that depends on kirigami for instance.
If we can't find a better solution, then at least it should be documented in the ECM android stuff to NOT put qml files into a .qrc...
So far we've worked with the assumption that you'd install the applications into a prefix then ran androiddeployqt over this file.
Well, that's exactly what I was doing... but if the QML files are built into a .qrc rather than installed, then this fails.
(The assumption also requires that the install prefix is only used for one android app only, otherwise it would all get mixed up)
Yes, that's what I meant.
So far we've worked with the assumption that you'd install the applications into a prefix then ran androiddeployqt over this file.
Well, that's exactly what I was doing... but if the QML files are built into a .qrc rather than installed, then this fails.
Yes, I understand your problem.
(The assumption also requires that the install prefix is only used for one android app only, otherwise it would all get mixed up)
Yes.
I've been thinking it through, I agree that the qrc use-case should be properly supported. Let's get this one in and if something's missing we can fix it in androiddeployqt.