Building Kivy app with Python3 for Android?

276 views
Skip to first unread message

Guido Muesch

unread,
Jan 28, 2018, 5:00:46 PM1/28/18
to Kivy users support
What's the recommended way?

I tried:
- Buildozer on Arch Linux: I've setup a Python3 venv in order to install Buildozer and additional packages => fails on crystax-ndk, because it seems to contain Python3.5, but Arch Linux has 3.6?
- Buildozer on Ubuntu 17.10: Similar issue
- Virtual Machine (for Android/buildozer): The Ubuntu in this VM is out of support since mid January 2018. I could not install additional packages.

Is there a newbie friendly way I am missing?

Cheers
Guido

ZenCODE

unread,
Jan 30, 2018, 1:08:37 AM1/30/18
to Kivy users support

Guido Muesch

unread,
Feb 1, 2018, 5:08:17 PM2/1/18
to Kivy users support


On Tuesday, January 30, 2018 at 7:08:37 AM UTC+1, ZenCODE wrote:

Thanks a lot. At least the example (touchtracer) works. Unfortunately my application immediatly exits. The output from "buildozer ... logcat" totally floods my terminal. So I could not find out the cause yet.
However, I specified "astropy" as a required package, which would in turn require Numpy. I am not sure if I need to specify it as well. If I do so, buildozer fails with:
"
[INFO]:    No existing dists meet the given requirements!
[INFO]:    No dist exists that meets your requirements, so one will be built.
[ERROR]:   Didn't find any valid dependency graphs.
[ERROR]:   This means that some of your requirements pull in conflicting dependencies.
[ERROR]:   Exiting.
"
Cheers
Guido

Guido Muesch

unread,
Feb 1, 2018, 5:27:17 PM2/1/18
to Kivy users support
OK, just found out that logcat output filtering can be specified in buildozer.spec:
"android.logcat_filters = *:S python:D"
That helps!

And it's indeed Numpy that is missing, but I have no clue yet how to prevent the above error message.

Guido

Alexander Taylor

unread,
Feb 3, 2018, 12:35:51 PM2/3/18
to Kivy users support
The numpy recipe is not currently compatible with python3crystax.

Guido Muesch

unread,
Feb 9, 2018, 4:46:40 PM2/9/18
to Kivy users support
Very unfortunate! It does not look like it gets fixed anytime soon. It's broken for Python3 for at least a year from what I see.
It would have been quite handy to do some image processing. A lotof other packages also depend on Numpy.

Switching back to 2.7.x is also not really a road I want to travel.

Why is it currently incompatible? Probably not something simple. It would have been fixed by now.

Cheers
Guido
Reply all
Reply to author
Forward
0 new messages