#!/usr/bin/env bash
# Build the gallery Android APK (and optionally install it).
#
#   ./scripts/build.sh              # release x86_64 (emulator) + install
#   ./scripts/build.sh aarch64      # release aarch64 (real device) + install
#   ./scripts/build.sh debug        # debug x86_64 + install (faster builds)
#   ./scripts/build.sh <arch> no-install
#
# Desktop (Linux): cargo run   (needs libfontconfig1 + pkg-config)
# Desktop (macOS): cargo run   (pure Rust, nothing extra)
set -euo pipefail
cd "$(dirname "$0")/.."

export ANDROID_HOME=$HOME/android-sdk
export ANDROID_NDK_ROOT=$HOME/android-sdk/ndk/27.0.12077973
# ~/.local/bin: nasm (host build of libjpeg-turbo SIMD; aarch64 needs no nasm).
export PATH="$HOME/.local/bin:$HOME/.cargo/bin:$ANDROID_HOME/platform-tools:$PATH"

# turbojpeg (M2): build the vendored libjpeg-turbo with CMake, statically linked
# into the app (no extra .so in the APK). The NDK CMake toolchain + ANDROID_*
# vars are picked up by the `cmake` crate; verified 2026-10 (HANDOFF §10).
if [ -n "$ANDROID_NDK_ROOT" ]; then
  export CMAKE_TOOLCHAIN_FILE=$ANDROID_NDK_ROOT/build/cmake/android.toolchain.cmake
  export ANDROID_PLATFORM=android-26
  export ANDROID_STL=c++_static
  export TURBOJPEG_STATIC=1
fi
# SDK platform used to compile the Slint Java helper (target API, matches
# target_sdk_version in Cargo.toml). Must be an installed platform dir.
SDK_PLATFORM=android-35

# Slint's android-activity build reads ANDROID_JAR first; setting it explicitly
# lets us ALSO export ANDROID_PLATFORM=android-26 below (for the NDK CMake
# toolchain's native API level) without the two tools fighting over that
# variable (`android-build` would otherwise look up platforms/android-26).
export ANDROID_JAR=$ANDROID_HOME/platforms/$SDK_PLATFORM/android.jar

# C/C++ cross-compilers for bundled native deps (libsqlite3-sys via rusqlite).
# The `cc` crate picks these up per target triple (min sdk 26).
NDK_BIN=$ANDROID_NDK_ROOT/toolchains/llvm/prebuilt/linux-x86_64/bin
# CMake target ABI (x86_64 default; overridden below for aarch64).
export ANDROID_ABI=x86_64
export CC_x86_64_linux_android=$NDK_BIN/x86_64-linux-android26-clang
export CXX_x86_64_linux_android=$NDK_BIN/x86_64-linux-android26-clang++
export AR_x86_64_linux_android=$NDK_BIN/llvm-ar
export CC_aarch64_linux_android=$NDK_BIN/aarch64-linux-android26-clang
export CXX_aarch64_linux_android=$NDK_BIN/aarch64-linux-android26-clang++
export AR_aarch64_linux_android=$NDK_BIN/llvm-ar
# Debug-keystore signing is fine for personal use / Play internal testing.
export CARGO_APK_RELEASE_KEYSTORE=$HOME/.android/debug.keystore
export CARGO_APK_RELEASE_KEYSTORE_PASSWORD=android

arg1=${1:-x86_64}
arg2=${2:-install}

profile=--release
features=perf
case $arg1 in
  debug)              target=x86_64-linux-android; profile="" ;;
  debug-aarch64)      target=aarch64-linux-android; profile=""; export ANDROID_ABI=arm64-v8a ;;
  x86_64)             target=x86_64-linux-android ;;
  aarch64)            target=aarch64-linux-android; export ANDROID_ABI=arm64-v8a ;;
  # Baseline-60 CONTROL build (2026-11-01): stock crates.io Slint (the
  # vendored [patch.crates-io] section is stripped from the manifest for
  # this build only), no driver/vkshim/instrumentation, display locked to
  # 60 Hz (src/baseline60.rs). Answers: does the grid jank WITHOUT our
  # vendored stack? Run: ./scripts/build.sh baseline
  baseline)           target=aarch64-linux-android; export ANDROID_ABI=arm64-v8a
                      features="baseline60,framelog"
                      cp Cargo.toml Cargo.toml.vendored.bak
                      python3 - Cargo.toml <<'PY'
import re, sys
p = sys.argv[1]
t = open(p).read()
i = re.search(r"^\[patch\.crates-io\]", t, re.M)
assert i, "vendored patch section not found — Cargo.toml layout changed?"
open(p, "w").write(t[:i.start()].rstrip() + "\n")
PY
                      trap 'cp Cargo.toml.vendored.bak Cargo.toml && rm -f Cargo.toml.vendored.bak' EXIT ;;
  *) echo "unknown arch: $arg1" >&2; exit 1 ;;
esac

profile_dir=release; [ -z "$profile" ] && profile_dir=debug

# Optional: ADB_SERIAL picks the device when several are attached (see AGENTS.md).
adb=(); [ -n "${ADB_SERIAL:-}" ] && adb=(adb -s "$ADB_SERIAL")

# Jank-hunt: rebuild the Vulkan interposer shim for THIS target ABI before
# cargo — src/vkshim.rs embeds shim/out/libvulkan.so via include_bytes!, so a
# stale/wrong-ABI shim would break the app at dlopen time. (Single-target
# builds only; a universal APK would need one shim per ABI — see vkshim.rs.)
mkdir -p shim/out
"$NDK_BIN/${target}26-clang" -shared -fPIC -O2 shim/vkshim.c -o shim/out/libvulkan.so -lunwind
echo "shim: $(du -h shim/out/libvulkan.so | cut -f1) for ${target}"

cargo apk2 build $profile --target "$target" --lib --features $features
apk=target/$profile_dir/apk/gallery.apk
echo "APK: $apk ($(du -h "$apk" | cut -f1))"

if [ "$arg2" = install ] && command -v adb >/dev/null; then
  "${adb[@]}" install -r "$apk"
  "${adb[@]}" shell am start -n wow.gmp.gallery/android.app.NativeActivity || true
fi