Skip to content

build(macos): bundle the terminal player as a relocatable app - #143

Closed
aRustyDev wants to merge 10 commits into
talwat:mainfrom
aRustyDev:stack/4/macos-app-pkg
Closed

aRustyDev wants to merge 10 commits into
talwat:mainfrom
aRustyDev:stack/4/macos-app-pkg

Conversation

@aRustyDev

@aRustyDev aRustyDev commented Oct 30, 2026 •

Copy link
Copy Markdown

TL;DR

Build a relocatable Lowfi.app that users can open from Finder or Spotlight. Launching it opens Lowfi's existing interface in Terminal.app.

Important

#blocked-by #139 (which is blocked by #138)

Please wait for #138 and #139 to merge before reviewing this PR. The Files changed tab includes their configuration and testing work because this PR targets main. After they merge, I’ll rebase this branch so the diff contains only terminal application packaging.

Packaging is independent of #140 and #142. Incremental packaging diff for reference.

Changes

  • Add packaging/macos/build-app.sh to build both executables, assemble the plist and icon assets, and verify the bundle before placing it under target/<native-target>/release/bundle/Lowfi.app.
  • Add an optional macos-app launcher binary. Resolve the bundle from the launcher's own location, then open its Lowfi.command in Terminal.app; the script starts the bundled lowfi.
  • Set default-run = "lowfi" so adding a second binary preserves plain cargo run.
  • Document installation and icon generation. Add macOS bundle CI and a Linux compile check for the launcher's non-macOS path.
  • Explain the launch chain, bundle-relative paths, argument handling, and verification limits in source/script comments. The smoke checks exercise the bundled player and script; they do not establish Finder or Terminal behavior.

Why this approach

A command-line binary is awkward to discover and launch through Finder or Spotlight. A thin application bundle provides that entry point while preserving Lowfi's terminal controls and configuration.

Wrapping the existing executable avoids maintaining a second UI or making packaging depend on the menu bar feature. Paths relative to the bundle allow relocation and avoid relying on a separate installation or shell PATH. Building the bundle locally keeps installation and signing explicit; the script does neither automatically.

Validation

Built and verified the standalone bundle on macOS: plist/version fields, executable permissions, icon conversion, help/version execution, relocation with spaces/Unicode/apostrophes, and failure when the player executable is missing. Cargo/Nextest suites and feature checks passed; the launcher also compiles on Linux. Opening a live Terminal session was exercised, opening while an existing player is running creates two players.

For this documentation update, private-item rustdoc passed with broken links denied, and shell syntax checks passed. The bundle and live GUI checks above were not repeated.

@aRustyDev aRustyDev changed the title Package an optional macOS terminal app bundle Build a relocatable macOS app for the terminal player Oct 30, 2026
@aRustyDev aRustyDev changed the title Build a relocatable macOS app for the terminal player build(macos): bundle the terminal player as a relocatable app Oct 30, 2026
@aRustyDev
aRustyDev force-pushed the stack/4/macos-app-pkg branch from 54a4d98 to ac49c94 Compare October 30, 2026 03:33
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.

2 participants