-
Notifications
You must be signed in to change notification settings - Fork 523
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
android.p4a_dir use old toolchain? #325
Comments
It built what you told it to build - the |
And don't run buildozer as root! It gives that warning for a reason. |
I used both. But distribute.sh should be obsolete? or i'm wrong? idk why this error |
The |
If i use the old toolchain with android.p4a as above i receive the distribute.sh problem, instead if i use the new toolchain it is builded with default python implementation (so ignore the android.p4a parameter). This is normal? |
What you described above is using old toolchain and pointing android.p4a_dir to the new toolchain. This obviously won't work. The new toolchain target (android_new) does not ignore android.p4a_dir at all, I've used this myself. |
My path point to this pull kivy/python-for-android#693 Please, you could give me the path you've tested? |
Either point android.p4a_dir to a clone of the old toolchain, and use the |
Probably not very relevant but, if you use the spec
android.p4a_dir
( for exampleandroid.p4a_dir = /usr/local/lib/python2.7/dist-packages/pythonforandroid/
) the buildozer build your app with the old toolchain regardless of the parametersandroid/android_new
.I said that because i receive the following error:
buildozer version:
Any confirmation / denial?
The text was updated successfully, but these errors were encountered: