https://bugs.kde.org/show_bug.cgi?id=491392
Freya Lupen <penguinflyer2...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |penguinflyer2...@gmail.com
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
--- Comment #1 from Freya Lupen <penguinflyer2...@gmail.com> ---
QML isn't being packaged. The .so files that go in /lib and the .qml and other
files that go in /assets/qml are missing.
Running androiddeployqt with --verbose, like
> $SRCDIR/_install/bin/androiddeployqt --input
> $SRCDIR/_build/krita-deployment.json --output $SRCDIR/_build/krita_build_apk/
> --android-platform android-34 --gradle --verbose
shows
> Running qmlimportscanner with the following command:
> /krita/_install/bin/qmlimportscanner -rootPath /krita/ -importPath
> /krita/_install/qml /krita/ /krita/_build/lib
> -- Adding '/krita/_install/qml/QtQuick.2' as QML dependency
> -- Skipping because path is in QML root path.
[... long list of QML dependencies being skipped]
qml-root-path is defined in _build/krita-deployment.json, which is generated by
ECM, which hardcodes this value to the source folder
(https://invent.kde.org/frameworks/extra-cmake-modules/-/blob/v5.101.0/toolchain/deployment-file-qt514.json.in?ref_type=tags).
Modifying this path to "[source]/plugins" (where Krita's own qml files are
located) produces an APK with a working Text Properties docker.
So patching ECM to make qml-root-path customizable would be one possible
solution, though there may be a better way.
--
You are receiving this mail because:
You are watching all bug changes.
