-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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 cross-compile #5242
Android cross-compile #5242
Conversation
…iples For cross compiling to targets that don't want to build a compiler
wow, amazing! I'll try to review this tomorrow; a little too exhausted tonight |
This will possibly require some tweaking to the bot configuration, particularly for snapshots. After this patch the |
@yichoi's branch and mine have diverged again so I'm going to spend some time today merging them |
I'll reopen another one later. |
add test for rust-lang#5238 changelog: none
r? @graydon
This is the bulk of the makefile work necessary to support cross-compiling with multiple toolchains. With this we can cross-compile to Android, but not run the test suite on Android. There is still some polish yet to add, but I want to get this merged.
Key changes:
As an example, to cross-compile to android, you configure with ../configure --target-triples=arm-unknown-android --android-ndk-path=~/dev/android-standalone-ndk-14. In this case the build triple and the host triples are automatically inferred, and the build triple added to the target triples, so if you are running on x86_64-unknown-linux-gnu, build-triple=x86_64-unknown-linux-gnu, host-triples=x86_64-unknown-linux-gnu and target-triples=x86_64-unknown-linux-gnu,arm-unknown-android.
This also changes the libuv remote back to
git://github.com/brson/libuv.git
to accommodate android fixes.Thanks to @yichoi who did most of this work.
Issue #4513.