-
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
x86 inline assembly fails to build #1238
Comments
Is it deliberate that you're using the pygame bootstrap here, rather than the sdl2 one? |
Yes, but when I used the sdl2 one, I got other issues. See #1233. SDL2 builds were successful, but the ctypes module failed to end up in the APK, so it did not run. I decided to test Pygame, when I did not get a response on that issue for a week. Give me a moment, and I will try pairing the sdl2 bootstrap with Pygame for the graphics. |
It failed for x86:
Now building for ARMv7. |
The ARMv7 build had the same result. (At least they both agree now!) |
Thanks for checking. I don't really know what's wrong in either case, but I'll try to look into it if I can reproduce the issue. |
I am willing to do a little bit more to help you debug, but only if it can happen fast. I have spent almost 3 weeks trying to get an Android build system setup, and a few days ago, I finally got the C/C++ one working. I would rather use Python, but with the time I have already spent trying to get this to work... At this point, I just need to get started working on my project. In another issue, I said I am deleting the entire build system for this. I'll wait until tomorrow or Monday maybe. If no progress has been made by then, I am afraid I am going to have to just drop this entirely so I can get my project going. Thank you for responding. |
Thanks for your patience, but to be honest it's unlikely that I'll look into this before then. However, your thorough reports probably have any necessary information already. Good luck with your project. |
Sounds good. Thank you for letting me know. Maybe this will be suitable for my next project then! |
Closing as stale, these issues may well have been addressed by the many improvements in the last year. |
It looks like I won't be able to use python-for-android for my project. It is way too buggy, the issues I have posted have not gotten any response, and it looks like the project has been dead since November.
I will post my issues though, in case someone eventually cares.
To start with, this issue is part of a string of issues. See #1233 for where I left off. (The most important thing from that is that I had to copy an asm directory from the i686 includes into sysroot/usr/include to get it past a problem finding types.h. I don't think this is related to that, but it could be.
The text was updated successfully, but these errors were encountered: