compile failing about python-for-android

[tito]

What's your Android SDK/NDK ? Did you correctly setup both of them ? Did you download one android platform with SDK android tool ?

[mulonemartin]

I switched to androidapi=14 and all went fine. I was using androidapi=15

[olymk2]

I can report the same issue, fails with androidapi 15, but works fine with 14 may be worth a note or something for anyone new setting up the enviroment.

[tito]

Ok, after checking, android api 15 cannot be used cause it doesn't exist in NDK r7 (r7 was released before SDK 15). Adding a tip about it in the doc

[tito]

added in doc

[yurkomik]

Same issue with android api 15 and kivy_stable, kivy compiled ok but had some errors later: import error for lang ets. I have latest SDK and NDK 8.

[yihuang]

Same issue here with android api 18 and ndk r8b.

[yihuang]

It turns out i need to set api to 14 instead of 18, though the sdk i use is api-18.

[sheldonrucker]

I was seeing the same "configure: error: C compiler cannot create executables" issue. After a bit of searching and looking at the output log I finally realized it was due to a permission issue. The configure script was trying to copy files to a directory but didn't have proper permissions. I fixed the issue by changing the ownership of the python-for-android directory to my user name. (chown -R "usernmae" python-for-android)

Thought I'd post this here in hopes it'll save someone else a bit of time. :-)

[mraygalaxy]

More information for those googlers: You're not constrained to API 14 - you just need to go to android developer website and download the latest NDK (not SDK, NDK) and then upgrade the your environment variables to point to the new NDK location (and new API level) and then re-run ./distribute.sh -m...... And everything works fine.

[brousch]

The easiest way to do it these days is to switch to buildozer instead of
bare python-for-android compiling, and use the default SDK and NDK settings
in buildozer. You don't even need to download the SDK and NDK because
buildozer will get them by itself.

On Sun, May 25, 2014 at 5:45 AM, Michael R. Hines
[email protected]:

More information for those googlers: You're not constrained to API 14 -
you just need to go to android developer website and download the latest
NDK (not SDK, NDK) and then upgrade the your environment variables to point
to the new NDK location (and new API level) and then re-run ./distribute.sh
-m...... And everything works fine.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-44127057
.

Ben Rousch
[email protected]
http://clusterbleep.net/