makiolaj/agendula
1
0
Fork 0
Code Issues Pull Requests Actions Releases 7 Activity

docs: note the ARM64 box64 aapt setup and the exit-code trap it causes

Browse Source
This commit is contained in:
Jean-Luc Makiola
2026-08-13 17:33:36 +02:00
parent 90140112bb
commit faee90f8b1
1 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
CLAUDE.md
View File

@@ -1,3 +1,19 @@
## Build host (ARM64)
The primary dev machine is ARM64 (aarch64) Linux, and Google ships no
linux-aarch64 `aapt`/`aapt2` — both run under **box64** via wrappers that live
outside the repo (`~/.gradle/box64-aapt2/aapt2` behind
`android.aapt2FromMavenOverride`, and an `aapt` wrapper installed straight into
`~/Android/Sdk/build-tools/*/` because AGP's test-APK installer hardcodes that
path). Nothing in the project tree depends on this; x86-64 machines and CI are
unaffected.
The trap: without the `aapt` wrapper, `connectedDebugAndroidTest` **exits
non-zero even when every test passes** — teardown fails, and Gradle reports it as
"There were failing tests". If that shows up, read
`app/build/outputs/androidTest-results/connected/debug/*.xml` for the real
result before believing the exit code.
## On-device work (USB-connected phone)
A physical phone is connected over USB. Rules: