From 171702bef43b844d9710ef0acee171afd4c3003f Mon Sep 17 00:00:00 2001 From: iChris4 Date: Sat, 26 Sep 2026 20:32:03 +0200 Subject: [PATCH] Name the per-variant game kit export task in the Quest docs The headset flavours split the kit export into one task per variant, which picks the CMake tree by the flavour's MKW_ANDROID_CPU. Co-Authored-By: Claude Opus 5.5 --- docs/quest-port.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/quest-port.md b/docs/quest-port.md index 4e51234..d135c3e 100644 --- a/docs/quest-port.md +++ b/docs/quest-port.md @@ -819,7 +819,10 @@ Android facts this design rests on, all measured on a Quest 3: `app/src/main/cpp/CMakeLists.txt` adds the repository's `runtime/` as a subdirectory with those Android choices and builds both game kit probes (the Retro Rewind one only when the translation includes the mod), which - `exportDebugQuestGameKit` turns into the single kit the app carries. + each variant's `exportQuestGameKit` task (for example + `exportModernQuestDebugQuestGameKit`) turns into the single kit that + variant's APK carries, read from the CMake tree whose `MKW_ANDROID_CPU` + matches the flavour. - `android/nod-jni`: Gradle's `buildNodJni` task runs `cargo build --release --locked --target aarch64-linux-android` with the NDK's clang as linker and C compiler. `stageNodJni` puts `libnod_jni.so` into the APK's `arm64-v8a`