You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just tested with Android NDK 19 for which we'll need to build with clang only. This seemed to work fine when I tested some core recipes (exception libFFI, #1612). However, to accomplish that I hardcoded clang=True in Arch.get_env.
We should only need to add a simple check for what is available in the NDK when selecting an appropriate compiler. Probably we should switch to clang-by-default even on NDKs where we currently use gcc.
The text was updated successfully, but these errors were encountered:
I just tested with Android NDK 19 for which we'll need to build with clang only. This seemed to work fine when I tested some core recipes (exception libFFI, #1612). However, to accomplish that I hardcoded clang=True in Arch.get_env.
We should only need to add a simple check for what is available in the NDK when selecting an appropriate compiler. Probably we should switch to clang-by-default even on NDKs where we currently use gcc.
The text was updated successfully, but these errors were encountered: