Build Frame Home payload in CI
Build the ARM64 headset payload against the glibc 2.39 baseline, validate its ABI,
and pass the generated artifact to Studio packaging.
Add provenance attestations and document CI and local build modes.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
GitHub's Windows runners are x64, so arm64 is a cross build. vcvarsall
sets up the ARM64 compiler, but CMake still reported the build machine's
own CPU (AMD64) as the target. astcenc then built its SSE4.1 version and
opus turned on its x86 SIMD files, neither of which compiles for ARM.
build_windows.bat now passes CMAKE_SYSTEM_NAME/CMAKE_SYSTEM_PROCESSOR
whenever the target differs from the build machine (arm64 from x64,
x86 from x64, x64 from an ARM PC).
Checked with MSVC 14.51: arm64 failed before this and builds after it
(the exe is ARM64); x86 and x64 still build.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Frame Studio now builds for Windows (x64, x86, ARM64), Linux (x64, x86, ARM64)
and macOS (Apple Silicon, Intel):
- studio/platform.h with Win32 and POSIX implementations (dialogs through
tinyfiledialogs on Linux/macOS), a GLFW window beside the Win32 one, and a
platform-neutral frame pacer
- MoltenVK support in the renderer (portability enumeration) and bundled in
the macOS app
- 32-bit builds: large-address-aware, LZMA packing within a 32-bit address space
- unaligned file reads in the loaders go through loadUnaligned (no UB)
- scripts/build-studio.sh, studio/build_windows.bat [x64|x86|arm64],
cmake/llvm-mingw.cmake, and a GitHub Actions workflow building every target
Frame Home installs without Studio: frame/install-frame-home.{sh,ps1} and
"Install Frame Home.bat" (packaged as FrameHome-installer.zip).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
