Skip to content
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

Closed
Tungsteno74 opened this issue Apr 22, 2016 · 8 comments
Closed

android.p4a_dir use old toolchain? #325

Tungsteno74 opened this issue Apr 22, 2016 · 8 comments

Comments

@Tungsteno74
Copy link

Tungsteno74 commented Apr 22, 2016

Probably not very relevant but, if you use the spec android.p4a_dir ( for example android.p4a_dir = /usr/local/lib/python2.7/dist-packages/pythonforandroid/) the buildozer build your app with the old toolchain regardless of the parameters android/android_new.

I said that because i receive the following error:

valerio@valerio-virtual01-xubuntu:~/PROGETTI/opentest$ sudo -H buildozer android debug
# Check configuration tokens
Buildozer is running as root!
This is not recommended, and may lead to problems later.
Are you sure you want to continue [y/n]? y
# Ensure build layout
# Check configuration tokens
# Preparing build
# Check requirements for android
# Run 'dpkg --version'
# Cwd None
Debian "dpkg", programma di gestione dei pacchetti versione 1.17.5 (amd64).
Questo è software libero; consultare la GNU General Public Licence versione 2
o successiva per le condizioni di copia. NON c'è alcuna garanzia.
# Search for Git (git)
#  -> found at /usr/bin/git
# Search for Cython (cython)
#  -> found at /usr/local/bin/cython
# Search for Java compiler (javac)
#  -> found at /usr/lib/jvm/java-7-oracle/bin/javac
# Search for Java keytool (keytool)
#  -> found at /usr/lib/jvm/java-7-oracle/jre/bin/keytool
# Install platform
# Apache ANT found at /root/.buildozer/android/platform/apache-ant-1.9.4
# Android SDK found at /root/.buildozer/android/platform/android-sdk-20
# Android NDK found at /root/.buildozer/android/platform/android-ndk-r9c
# Check application requirements
# Run './distribute.sh -l'
# Cwd /usr/local/lib/python2.7/dist-packages/pythonforandroid/
/bin/sh: 1: ./distribute.sh: not found
# Command failed: ./distribute.sh -l
# 
# Buildozer failed to execute the last command
# The error might be hidden in the log above this error
# Please read the full log, and search for it before
# raising an issue with buildozer itself.
# In case of a bug report, please add a full log with log_level = 2

buildozer version:

sudo buildozer version
# Check configuration tokens
Buildozer is running as root!
This is not recommended, and may lead to problems later.
Are you sure you want to continue [y/n]? y
Buildozer 0.32dev

Any confirmation / denial?

@kived
Copy link
Contributor

kived commented Apr 22, 2016

It built what you told it to build - the android target. You need to use the android_new target to use the new toolchain.

@kived kived closed this as completed Apr 22, 2016
@kived
Copy link
Contributor

kived commented Apr 22, 2016

And don't run buildozer as root! It gives that warning for a reason.

@Tungsteno74
Copy link
Author

I used both. But distribute.sh should be obsolete? or i'm wrong? idk why this error
in any case thanks

@kived
Copy link
Contributor

kived commented Apr 22, 2016

The android target uses the old toolchain, with distribute.sh. The android_new target uses the new toolchain, without distribute.sh.

@Tungsteno74
Copy link
Author

Tungsteno74 commented Apr 22, 2016

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?

@kived
Copy link
Contributor

kived commented Apr 22, 2016

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.

@Tungsteno74
Copy link
Author

Tungsteno74 commented Apr 22, 2016

My path point to this pull kivy/python-for-android#693

Please, you could give me the path you've tested?

@kived
Copy link
Contributor

kived commented Apr 22, 2016

Either point android.p4a_dir to a clone of the old toolchain, and use the android target, or else point android.p4a_dir to a clone of the new toolchain, and use the android_new target.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants