Antra::Packer

Ready-to-run app folders and archives: antra pack.

pack puts everything a program needs into one folder per target platform and packs it as .zip (Windows) or .tar.gz:

dist/breakout-windows-x86_64/
  breakout.exe       the antra runtime, renamed — double-click starts the app
  antra-app.txt      tells the runtime which script to run
  lib/Antra/         the standard library
  app/               the project: scripts, assets, its own lib/
  app/native/windows-x86_64/   the C libraries from native.and
  licenses/          antra's and the libraries' license notices

Every target is built from every system: the runtime for another platform comes from the antra release of the same version (cached like native libraries, ANTRA_CACHE), native libraries from antra native install.

Settings come from the command line or an optional app.and next to the main script:

# antra pack settings
%Packer{name: "breakout", main: "breakout.ant", version: "1.0",
        targets: ["windows-x86_64", "linux-x86_64", "macos-aarch64"],
        exclude: ["tests", "*.tmp"]}

Written as %Packer{...} the file says what it is; plain %{...} works as well.

The packed app starts in the folder of its main script (cwd: "main", the default), so relative paths like "resources/ball.png" work as in development; cwd: "keep" keeps the caller's directory (command-line tools that take file arguments). System.script_dir() finds the app's files either way.

With macos_app: true (or --macos-app) a macOS target becomes an app bundle that starts with a double-click:

dist/breakout-macos-aarch64/Breakout.app/Contents/
  Info.plist         name, bundle id, version, icon
  MacOS/breakout     the antra runtime, with antra-app.txt next to it
  Resources/         lib/Antra/, app/, licenses/, the icon

display_name names the bundle (default: name), bundle_id sets CFBundleIdentifier, icon is a PNG (16 to 1024 pixels square, or a list of them) or an .icns file. Output goes to ~/Library/Logs/<name>.log when the app runs without a terminal. On a Mac the bundle is signed ad hoc (codesign -s -).

With onefile: true (or --onefile) the app is a single executable: the runtime with its files appended as one payload. It unpacks them on the first start into the cache (ANTRA_CACHE, else %LOCALAPPDATA%\antra\cache or ~/.cache/antra, in apps/<hash>/) and runs from there. On macOS an appended payload would break the code signature, so the payload is an app.pack file next to the executable (in Contents/Resources/ of a bundle).