Skip to main content
The main build packs files.source with the x64 setup runtime. [arch.arm64] names the ARM64 build of the same app, and bach build then also writes an ARM64 setup file, built on the ARM64 runtime, and lists both in the update feed.
bach.toml
  • The ARM64 runtime is in every release’s bach-<version>-windows-arm64.zip. Bach checks that it is an ARM64 program and refuses an x64 one. --x64-only builds only the x64 file.
  • Both setup files carry the same app id and version. The ARM64 file is named Hello-Setup-1.4.0-arm64.exe.
  • latest.json keeps the x64 file as its main entry and adds arch.arm64 with its own link, SHA-256, size and, with [updates] public_key, its own signature. Older apps ignore it and keep taking the x64 file.
  • The online installer is built once and asks Windows what the computer is, so on Windows on ARM it downloads the ARM64 file. An installed app updates with the architecture it was installed with.
  • bach feed SETUP.exe --arm64 SETUP-arm64.exe writes the feed with the ARM64 listing when you build the files separately.