-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
buildozer build failed with python3 #264
Comments
full build log of third command is https://pastebin.com/SARXAjR2 |
Can you build a regular non-kivent kivy app? |
I assume yes, as described in "run buildozer" step, I was able to build with kivy only in requirements. |
Is Kivy installed in the Python3.5 that is running buildozer? |
No, only buildozer and cython==0.25.2 is installed there. And buildozer is installed in python2.7 (although I tried to uninstall python2, install python3-pip, link /usr/bin/pip3 to /usr/bin/pip and do steps above, and the same results) |
1 year ago |
Everything works ok with py2, but when I tried to build with python3 I got such error:
Steps to reproduce:
make chroot
configure schroot
install schroot and create file /etc/schroot/chroot.d/buildozer.conf with such contents:
of course replace /home/maho with appropriate /home/username, the same with users and groups
install neccesary software in chroot
Install cython and buildozer in chroot's pip
Unpack ndk
Download Crystax NDK and unpack into ~/ndk/crystax-ndk-10.3.2/
Make bare app
and then
then edit buildozer.init and place following lines into it:
Note, that there is no cymunk nor kivent_core in requirements, it's because of issue in kivy/python-for-android#1184
Clean everything in ~/.buildozer
rm -rf ~/.buildozer .buildozer
just in case, to be sure you have fresh installarun buildozer
succeeded, althouth there error in the end, which I think can be ignored:
add cymunk to requirements and run buildozer again
in /buildozer.spec/ now you should have:
add kivent_core to requirements and run buildozer again
in /buildozer.spec/ now you should have:
The text was updated successfully, but these errors were encountered: