-
Notifications
You must be signed in to change notification settings - Fork 240
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
Move android toolchain to use r11 #625
Comments
So they changed the entire directory structure in r11(a/b/c), plus moved On the other hand, we should definitely find more robust way of bypassing this I am going to park this issue for the time being, or until we have a pressing reason to move to a newer ndk release. Refer: taka-no-me/android-cmake#81, (this also have some hacky way of getting the toolchain to work, but I do not think we should adopt this approach). |
Fascinating! Makes sense to put this on standby. Part of me would like to use the Or we could move everything to Bazel! ;) |
Doing some research over that, it seems that this project have an updated version using r11 in their cmake toolchain https://github.com/urho3d/Urho3D. It would be worth trying this before investing more work towards moving to a different build system for android. |
Android Studio 2.2 supports CMake integration out of the box, we should wait until it's released and use that for our build toolchain instead: http://tools.android.com/recent/androidstudio22preview3available |
Our android build system is through new android studio and using gradle native builds, which will make sure we are upto date with NDK versions. |
Android ndk got upgraded to r11. Tangram-es is currently using r10e.
Update to use r11.
http://developer.android.com/ndk/downloads/index.html
The text was updated successfully, but these errors were encountered: