Setupidity separates where an installer is authored from where that installer runs. Keeping those two roles distinct prevents misleading compatibility claims.
Authoring hosts
- Windows x86-64: native executable and containerized workflow.
- Linux x86-64: native executable and the pinned build container.
- macOS Apple Silicon and Intel: native command-line builds; distribution requires signing and notarization outside Setupidity.
Docker can build all targets from the same Linux toolchain image. A binary must match the host processor architecture; it does not determine the target of the generated package.
Installer target and runtime
Every generated .msi targets 64-bit Windows Installer. Linux and macOS can author and inspect packages, but they cannot execute the Windows installation. Test install, repair, upgrade, rollback, and uninstall on the Windows versions your application supports.
Interactive pages appear only during a full UI install. /qn silent installs and /a administrative images do not display Setupidity’s authored UI. Per-machine installation writes under Program Files by default and requires elevation.
Platform-specific release work
Setupidity does not sign its own executable or the generated MSI. Apply your organization’s Windows code-signing process after creation. Native macOS builds likewise require the publisher’s signing and notarization before distribution.
Previous: Supported features · Next: Troubleshooting