Skip to content

feat: ship a macOS .dmg installer (WAIL.app with bundled libopus) - #515

Merged
quasor merged 1 commit into
mainfrom
wt-5
Aug 3, 2026
Merged

quasor merged 1 commit into
mainfrom
wt-5

Conversation

@quasor

@quasor quasor commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

What

Adds a real macOS download: wail-macos-arm64-<version>.dmg containing WAIL.app, built by a new scripts/package-macos.sh and a build-macos job in release.yml. Until now the only Mac install path was Homebrew building from source — which exists partly because the app links libopus dynamically from the Homebrew prefix.

How

scripts/package-macos.sh --version X.Y.Z --plugins DIR --out DIR:

  1. Builds the app with -tags nolibopusfile (so libopus is the only non-system dylib)
  2. Stages a standard WAIL.app — Info.plist, icon rendered from the frontend logo, and the CLAP plugins at Contents/lib (where the app's first-launch installer looks, via {exe}/../lib)
  3. Copies any package-manager dylibs into Contents/Frameworks and rewrites references to @executable_path — hand-rolled install_name_tool, no dylibbundler dependency; a post-check fails the build if any Homebrew reference survives
  4. Ad-hoc signs inside-out (dylibs → .clap bundles → app) and verifies with codesign --verify --deep --strict
  5. Wraps it in a UDZO dmg with an Applications symlink

Verified locally: mounted dmg, codesign --verify clean, and the bundled binary launches with the Homebrew opus prefix temporarily hidden (proving it loads libopus from inside the .app).

Deliberate trades

  • Apple Silicon only — Intel Macs stay on the Homebrew source tarball (noted in README).
  • Unsigned / not notarized — first launch is right-click → Open, same trade as the unsigned Windows build. Notarization (Developer ID + notarytool) can be layered on later without changing anything else.

CI

  • release.yml: new build-macos job (macos-latest → plugins → package script → artifact), wired into create-release's needs/condition/files like the other platforms — a failed mac build doesn't sink the release.
  • build.yml: the existing build-macos job now smoke-tests the packaging script end-to-end on PRs, so a broken script fails before release day.

Testing

  • Script verified locally (bundle + dmg + signature + no-Homebrew launch), with and without plugins
  • go test ./... ✅ · go test -tags linkstub ./... ✅ · relay tests ✅ · scripts/tier2-e2e.sh PASS ✅
  • Docs synced: README (install section), DEVELOPMENT.md (beta channel), CLAUDE.md (release pipeline)

macOS users previously had exactly one install path: Homebrew building
from source (which exists partly because the app links libopus
dynamically from the Homebrew prefix). This adds a real download:
WAIL.app inside a drag-to-Applications dmg.

scripts/package-macos.sh builds the app (nolibopusfile, so libopus is
the only non-system dylib), stages a standard bundle — Info.plist,
icon from the frontend logo, CLAP plugins at Contents/lib where the
first-launch installer finds them — copies any package-manager dylibs
into Contents/Frameworks and rewrites the references to
@executable_path (no dylibbundler dependency; a post-check fails the
build if any Homebrew reference survives), ad-hoc signs inside-out,
and wraps it in a UDZO dmg. Verified locally: the bundled binary
launches with the Homebrew opus prefix hidden.

release.yml gains a build-macos job wired into create-release like the
other platforms (a failed mac build doesn't sink the release). The
dmg is Apple Silicon only and unsigned — first launch is right-click,
Open, same trade as the unsigned Windows build; Intel Macs stay on the
Homebrew tarball. build.yml's build-macos job smoke-tests the script
on PRs so a broken package script fails before release day.
@quasor
quasor merged commit bce4082 into main Aug 3, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant