omar/panopainter
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Expose Windows package smoke as CMake target

Browse Source
This commit is contained in:
omigamedev
2026-06-05 12:51:25 +02:00
parent 97fd7de955
commit 3e5340b696
5 changed files with 25 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/modernization/build-inventory.md
View File

@@ -78,6 +78,7 @@ powershell -ExecutionPolicy Bypass -File scripts\automation\android-legacy-packa
powershell -ExecutionPolicy Bypass -File scripts\automation\package-smoke.ps1 -Preset windows-msvc-default -Configuration Debug
powershell -ExecutionPolicy Bypass -File scripts\automation\package-smoke.ps1 -ReadinessOnly
powershell -ExecutionPolicy Bypass -File scripts\automation\package-smoke.ps1 -ReadinessOnly -AndroidNativeChecks -PackageKinds android-standard-apk,android-quest-apk,android-focus-apk
cmake --build --preset windows-msvc-default --config Debug --target panopainter_windows_app_package_smoke
cmake --build --preset windows-msvc-default --config Debug --target panopainter_android_native_package_smoke
cmake --build --preset windows-msvc-default --config Debug --target panopainter_platform_build_android_assets
cmake --fresh --preset windows-clangcl-asan
@@ -191,6 +192,7 @@ powershell -ExecutionPolicy Bypass -File scripts\automation\apple-remote-build.p
validation target names.
- Root CMake exposes non-default package validation targets:
`panopainter_package_readiness`,
`panopainter_windows_app_package_smoke`,
`panopainter_android_standard_native_package`,
`panopainter_android_vr_native_package_configure`, and
`panopainter_android_native_package_smoke`. These targets call the automation