https://bugs.kde.org/show_bug.cgi?id=493806
Thomas Kuntz <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Thomas Kuntz <[email protected]> --- Hello, I worked on briging Python to android, here are the 3 PRs : - https://invent.kde.org/packaging/krita-ci-utilities/-/merge_requests/19 - https://invent.kde.org/packaging/krita-deps-management/-/merge_requests/90 - https://invent.kde.org/graphics/krita/-/merge_requests/2932 I had to update the build CI in those 3 repos because after cross compiling python for android, I encountered a lot of issue with build tools trying to use THIS Python for their python script, instead of the host one. Also cross compiling Python on android require the same version of Python on the host system, so I tried to normalize the build ci scripts to stop using system installed python and just base everything on the "host" Python. It all meant splitting the build & install folder in 2 to have a subfolder for host binaries (ie build tools) and target binaries & libraries. I'm of course willing to changes things, but I already tried "brut forcing" everything in a unique build/install folder, and it caused just so many small issues, I think keeping the split is better for cross compilation in general. I also know that having a version of Krita with Python on Google Play si big no no because it would allow the user to run unsigned code via the app, so I added a CMake var to disable the build ok PyKrita for android. But we can still build with PyKrita for F-droid for example, of just when distributing the APK outside of Google Play. -- You are receiving this mail because: You are watching all bug changes.
