irisandClaude Sonnet
ceabd00805
New xtask/ crate (no deps) runs cargo ndk -> javac -> d8 -> aapt2 -> zipalign -> apksigner directly, signed with the same key build-apk.sh uses. Both pass conditions proved on the ai-app-2 emulator: the xtask APK installs over the Gradle-built shellApp, and the notification service starts and posts a real notification while backgrounded. Adds one printRuntimeClasspathJars task to shellApp/build.gradle.kts (and a matching signingConfig) -- the one disclosed Gradle call the xtask still makes, to resolve the AndroidX/:link dependency graph. That call's Kotlin compilation of :link as a side effect also answers E3's open kotlinc question, so no Java port of ServerStore was needed. Wires a second Apk component into .dev-updater.ron beside the existing one. Full writeup in RUST.md's E5 box. Co-Authored-By: Claude Sonnet <noreply@anthropic.com>
76 lines
3.8 KiB
Plaintext
76 lines
3.8 KiB
Plaintext
// Read by Dev Updater. Structured as the body of the config: no outer
|
|
// parentheses, so nothing here is indented for the sake of a wrapper.
|
|
//
|
|
// This file sits at the checkout root because the project Dev Updater
|
|
// serves is the whole repository -- one checkout producing two things.
|
|
// Each component says where it lives with `cwd`, relative to this
|
|
// directory, rather than one of them reaching out of the other with `../`.
|
|
|
|
// What to call this project before there is a build to read a label from.
|
|
// A built APK wins: it is the authority on what will actually install.
|
|
label: "AI Sessions",
|
|
|
|
// Where this project's own state lives, said rather than guessed: it is
|
|
// what the Uninstall dialog offers to delete, and a plausible-looking
|
|
// path it worked out would read as "this component keeps nothing here"
|
|
// when it was wrong. `Ron` rather than `Script` because the answer is
|
|
// three constants -- there is nothing here worth spawning a process for.
|
|
resources: Ron("resources.ron"),
|
|
|
|
// The two halves this checkout produces: the server a phone talks to, and
|
|
// the app that talks to it. They are built in parallel -- this list is the
|
|
// set, not a sequence, so nothing here should be read as an order.
|
|
components: [
|
|
Server(
|
|
name: "server",
|
|
build: "cargo build --release",
|
|
cwd: "server",
|
|
// Dev Updater's own built-in service implementation, generated
|
|
// into its data directory and driven through the same interface a
|
|
// project-supplied script would be. ai-app carried a script of its
|
|
// own until 2026-08-28; it ran `target/release/ai-server` with no
|
|
// arguments and no environment, which is the generic case exactly,
|
|
// so it was two copies of one thing and the copy that could not be
|
|
// tested from here -- the OpenRC branch -- was duplicated with it.
|
|
//
|
|
// Resolved against this component's `cwd`, so this is
|
|
// `server/target/release/ai-server`.
|
|
service: Managed("target/release/ai-server"),
|
|
),
|
|
Apk(
|
|
name: "app",
|
|
// Release first: the first mode is the default, and the phone runs
|
|
// the release build -- a debuggable one runs Compose at a fraction
|
|
// of the speed. Each command below is run with the chosen mode as
|
|
// its last argument, which is exactly build-apk.sh's interface.
|
|
modes: ["release", "debug"],
|
|
// Resolved against this directory, and run in `app/` -- the script
|
|
// cds to its own directory anyway, so the cwd is here to say where
|
|
// the app is rather than because the build needs it.
|
|
build: "app/build-apk.sh",
|
|
cwd: "app",
|
|
// The Enroll button in this component's settings: prints the link
|
|
// that enrols the phone against the server built here, for the
|
|
// reinstalls -- a signing change, a new phone -- where nobody is at
|
|
// the terminal the QR would be printed on.
|
|
enroll: "server/enroll-link.sh",
|
|
),
|
|
// E5 (RUST.md): app/shellApp packaged by the xtask instead of Gradle
|
|
// (cargo ndk -> javac -> d8 -> aapt2 -> zipalign -> apksigner), signed
|
|
// with the same release key as "app" above so the two can install
|
|
// over each other -- a separate component, not a mode of "app" above,
|
|
// because it is a different applicationId (com.example.aiapp.shell)
|
|
// built by a different tool from different sources. No `cwd`: it
|
|
// defaults to this checkout's root, which both the `cargo xtask`
|
|
// alias (`.cargo/config.toml`, resolved relative to the working
|
|
// directory cargo is run from) and `cargo xtask apk`'s own publishing
|
|
// step (`xtask/build/outputs/apk/<mode>/*.apk`, matching discover.rs's
|
|
// `*/build/outputs/apk/*/*.apk` pattern -- see apk.rs's module doc)
|
|
// both need.
|
|
Apk(
|
|
name: "shell",
|
|
modes: ["release", "debug"],
|
|
build: "cargo xtask apk",
|
|
),
|
|
],
|