Repository navigation
Build and upload all Android artifacts on CI - #2
Merged
Merged
Conversation
1. Build Android libraries on Ubuntu, not macOS. It's cheaper to use Ubuntu. 2. Use latest NDK, which is r29. This means we get 16KB page support enabled by default. 3. Build two ABIs: arm64 and x86_64 4. Use the `scripts/android.py` script instead of invoking CMake directly. 5. Upload the resulting artifacts to GitHub actions. This includes all layers (even though we don't really need the api_dump layer, it's easier to build/upload it this way).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Build Android libraries on Ubuntu, not macOS. It's cheaper to use Ubuntu.
Use latest NDK, which is r29. This means we get 16KB page support enabled by default.
Build two ABIs: arm64 and x86_64
Use the
scripts/android.pyscript instead of invoking CMake directly.Upload the resulting artifacts to GitHub actions. This includes all layers (even though we don't really need the api_dump layer, it's easier to build/upload it this way).