Establish native Linux ARM64 Android CI and verification gates (#94)
Android ARM verification / rust (push) Failing after 7s
Android ARM verification / android (push) Failing after 7s

This commit is contained in:
hugo committed 2026-10-09 00:25:06 +02:00
1 parent 1abd75282e
commit b3853a75c8
29 files changed
+1864 -56

No files matched your search

+6 -5
View File
@@ -66,11 +66,12 @@ policy. The installed android-37.0 SDK reports an empty codename and
PreviewSdkInt=0 (revision 2); verify the same package metadata in CI before
pinning the build, rather than relying on preview wording in older instructions.
Release ABIs: **arm64-v8a**, **armeabi-v7a**, **x86_64**, corresponding to
**aarch64-linux-android**, **armv7-linux-androideabi**,
**x86_64-linux-android**. An ABI may be removed only with a dependency audit and
an amendment to this decision; emulator success alone proves no arm64 hardware
coverage. All shipped native dependencies, including JNA, must pass ELF LOAD
Release ABIs: **arm64-v8a** and **armeabi-v7a**, corresponding to
**aarch64-linux-android** and **armv7-linux-androideabi**. On 2026-10-08 the user
removed x86_64 Android from the support and CI requirements and specified
emulator-only testing for every issue. This supersedes the original three-ABI
decision in #88; historical test evidence remains historical.
All shipped native dependencies, including JNA, must pass ELF LOAD
alignment, APK ZIP alignment and actual 16 KB runtime checks. Do not depend on
compatibility mode. [Android's page-size guidance](https://developer.android.com/guide/practices/page-sizes)
requires auditing dependencies as well as the app library.