Release: build and ship the Android default library, collector and runtime

[ASDAlexander77]

What

The release workflow's Windows job (create-release.yml, build_on_windows) now also builds everything Android needs, after the desktop default library, with the runner's preinstalled Android NDK (ANDROID_NDK_LATEST_HOME, falling back to ANDROID_NDK_HOME):

1. Install Ninja (choco): the Android scripts use the NDK's CMake toolchain with Ninja.

2. Build Android Collector and Async Runtime: scripts\build_gc_release_android.bat and scripts\build_tslang_runtime_release_android.bat, for API 29, arm64-v8a and x86_64. It also exports ANDROID_NDK_HOME for the later steps.

3. Build Android Default Library: TypeScriptCompilerDefaultLib's scripts\build_android.bat with the tslang just built: both ABIs × release/debug × gc/rc/none.

4. Test Compiler for Android: test-compile-android-codegen and test-compile-android-link (an exe and a .so linked for x86_64 with the libraries just built). The step fails if the link test reports itself skipped, so missing libraries can't pass silently.

5. Packaging: the Windows zip gets, per ABI:

   • android/<abi>/defaultlib/... → --default-lib-path=android/<abi>
   • android/<abi>/lib/libgc.a, android/<abi>/lib/libTypeScriptAsyncRuntime.a → --gc-lib-path / --tslang-lib-path

   The Android trees are moved out of the default library's __build, which is packaged whole, so they aren't shipped twice.

Verification

This workflow runs only on a v* tag, so it can't run in this PR. I verified the new steps locally with the same commands:

• The Android scripts build both ABIs.
• ctest -R test-compile-android-: both pass, and neither is skipped.
• The staging script against copies of the trees gives the layout above, and nothing is left in the default library's __build.
• tslang --emit=exe and --emit=dll link for arm64-v8a and x86_64 using only the staged package paths.

What I couldn't check locally:

• the runner's NDK version (whichever is preinstalled; the scripts need r27+ for API 29 and were tested with r30);
• whether choco install ninja succeeds on windows-2025-vs2026.

Both show up early in the job log; the NDK revision is printed.

Related: #518 turns parallel marking off for the Android collector (bdwgc/bdwgc#980). Whichever version of that script is on main at release time is what this builds.

🤖 Generated with Claude Code