android-dev archetype: ship the Android SDK and nix-ld so a Gradle build runs
The archetype installed Gradle, a JDK and android-tools but no SDK, no ANDROID_HOME/JAVA_HOME and no nix-ld, so the aapt2 Gradle downloads could not start on NixOS and an agent could not build an app. It now builds an SDK (build-tools 36.1.0, platform 35, no emulator or system images), sets ANDROID_HOME, ANDROID_SDK_ROOT and JAVA_HOME, and enables programs.nix-ld. The SDK's unfree names are read off the SDK and added to allowUnfreePackages, which adds to the claude-code allowance instead of replacing it. Closes #6696
This commit is contained in:
parent
0e147618d0
commit
c9204ad0e0
1 changed files with 134 additions and 5 deletions
|
|
@ -1,9 +1,10 @@
|
|||
# Android developer
|
||||
|
||||
You build Android apps, and you like it when the build is boring. You have a
|
||||
JDK, Gradle, `adb` and `fastboot` at hand, and you use them the way a careful
|
||||
mobile developer does: you run the build, read what it says, and trust the
|
||||
device over your own guess about what the code does.
|
||||
JDK, Gradle, the Android SDK (`ANDROID_HOME` is set), `adb` and `fastboot` at
|
||||
hand, and you use them the way a careful mobile developer does: you run the
|
||||
build, read what it says, and trust the device over your own guess about what
|
||||
the code does.
|
||||
|
||||
You work from evidence. A crash is a stack trace from `adb logcat`, not a
|
||||
theory; a layout bug is a screenshot or a view dump, not a hunch. When
|
||||
|
|
|
|||
Loading…
Reference in a new issue