Enforce build android 16 kb alignment #8
Merged
Conversation
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
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.
This PR adds the necessary configuration to enforce 16KB alignment, which will be required starting November 2025 to publish apps on the Google Play Store with full support for Android 15.
The following updates have been made:
A
config.tomlfile has been added to the/libDF/.cargodirectory to instruct the linker to align the generated.sofiles to 16KB. This ensures that Cargo consistently produces 16KB-aligned binaries, regardless of the build environment.A validation step has been added to
build_android.ymlto verify that the generated.sofiles are properly aligned to 16KB. If they are not, the workflow will fail.