-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Uses Arm builds for x86, if Arm builds already exist #1233
Comments
Ok, i found the files in the APK. Buried deep in the documentation it says private.mp3 is where all the Python stuff and assets are, and my image file is in there. I am still struggling with getting it to display though. Now that I know where it is though, I might be able to figure out the path to it. |
I think I figured this out. My first builds were for Arm, because that is just the default I used. The tablet I am testing on uses x86, so I changed the arch to x86, but p4a was still building for Arm, because it found the Arm stuff already built. p4a clean_all should fix this (though I am getting another error...) |
OK, here is the other error:
I then ran find on my SDK directory, and it returned this:
(It also finds I am not sure which it is trying to find. All of the errors about "duplicate unsigned" and "two or more data types in declaration specifiers" are probably the result of this one header not being found. |
I have discovered a cheap hack that will allow x86 builds. I copied i686-linux-android/asm into the NDK include directory. The app still won't run on my device, but that's a separate issue that will bring up after troubleshooting, if I cannot figure it out. |
It looks like the issue with running the app on my device may be related to this after all, since it is an issue with ctypes. Alternatively, this could be a reversion of #333. (TL;DR: ImportError: No module named _ctypes)
I have attached the full debugger output, in case there is some value in having it. The compile command for the package is The target is x86. If it would help, I can run a clean build and upload the log of that as well. |
The cheap hack mentioned above does eliminate the error with finding asm/types.h. Instead I get #1238 now. (Also see #1239 for what happens when I try to build for ARMv7.) I am done with python-for-android. I have not managed to build anything yet, and it is clear no one cares about the project anymore. I have reported all of my issues, and I will give a little bit more background information here. Please don't bother asking me to post anymore debugging information. I would have been willing a week ago (when I first opened this report) all the way to yesterday, but I am now removing the entire p4a build system from my computer, so I can focus on focus on writing my app in C/C++. Here are my system specs, in case any of them make a difference: OS: Debian 9, Linux 4.9.30 I hope this helps someone at some point. |
Sorry that p4a didn't work out for you, thanks for the detailed reports in any case. I haven't seen an issue like this before (at least, not since ctypes support was first added). Since x86 builds haven't been tested much, maybe it's an issue with this in particular. I'll try to look into it. |
Honestly, in my experience, if there is a bug in a build environment I will find it. I have kind of gotten used to it at this point. I'll keep an eye on this. If this is fixed before I start my next project, I will try python-for-android again. |
x86 include folder has different name, possible solution GH-1252 |
Ok, so I am 90% sure this is a lack of documentation problem rather than a bug, but I have spent the last two hours trying to figure this out without any luck.
I have managed to write a simple PySDL2 program that loads an image file and displays it on the screen, however, it does not work on my device. It turns out that the image file is never put into the APK file.
At first, I put the file in
img/
. When this failed, I tried putting it in ares
directory and then in the project root. Then I spent a bunch of time trying to find an answer on Google, but I cannot even find an example of a program that works for python-for-android and loads an image file. (In fact, I couldn't fine a Kivy one or a PySDL2 one.)I would like to think I am in the home stretch (of a week long battle) for finding a tolerable Android development environment, but this is just another hurdle in the extremely long list. If anyone knows how to get p4a to put the image in the APK (and preferably also the path I should expect to be able to access it from in my code), that would really help me!
The text was updated successfully, but these errors were encountered: