-
Notifications
You must be signed in to change notification settings - Fork 506
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
Building apk with Windows Subsystem for Linux: sh.ErrorReturnCode_127 #1012
Comments
This is because you're missing some system dependencies, e.g. |
Thank you very much, @AndreMiras . Full log:
|
Yes it's also some missing system dependencies. |
Thank you again for your help @AndreMiras . Log:
Thanks for the time. |
make sure to do a clean build ( |
Sooo I did that, and now I have a syntax error which I feel is quite unrelated. I figured I might've messed something up with my python installations, as there really shouldn't be a syntax error unless maybe I'm implicitely running with an incompatible verison of python.
|
oh duh, it seems your buildozer is installed in python2.7, and so it tries to run p4a with 2.7 as well, wich doesn't work anymore as p4a is python3 only now, you should |
Thanks tshirtman, I hadn't thought it was buildozer itself that could be installed with a different version of Python.
Just to name a few. The conclusion is:
|
Yes buildozer no longer supports Python 2. |
Versions
Description
Hello there!
I'm trying to build an app's apk on Windows10 without doing a dual boot, which I feel incapable of doing and would rather avoid. I've read on a couple of places that there were ways to do that with Windows Subsystem for Linux.
I've followed the instructions of this video:
https://youtu.be/KQ68bJE8g7c
Then I had the issue "sdkmanager is notinstalled" (#927), which I think I solved by running:
After this I didn't get "sdkmannager is notinstalled" anymore, although I get a fairly lengthy error while trying to build the apk with
buildozer android debug
which I am not competent enough to describe better than the log.Thanks for reading.
buildozer.spec
Command:
Spec file:
Logs
The text was updated successfully, but these errors were encountered: