diff options
| author | user <user@clank> | 2026-08-28 15:38:27 +0200 |
|---|---|---|
| committer | user <user@clank> | 2026-08-28 15:38:27 +0200 |
| commit | 67e0330e5f18e4fe7f87db978071c6afa77ee91b (patch) | |
| tree | 73c544d533bead3c4f8cfdeff8c66de7b77df94a /docs | |
| parent | windows watcher: rebuild the watch set instead of freezing it (diff) | |
| download | slosh-67e0330e5f18e4fe7f87db978071c6afa77ee91b.tar.gz slosh-67e0330e5f18e4fe7f87db978071c6afa77ee91b.tar.xz slosh-67e0330e5f18e4fe7f87db978071c6afa77ee91b.zip | |
windows release: a zip in dist/, built beside the linux tarballs
make -f Makefile.windows dist stages slosh.exe as
slosh-<version>-windows-<arch>.zip -- a zip, not a tarball, because Windows
is the machine that will open it -- carrying the same licensing paperwork as
the linux tarballs, with docs/windows.md riding along instead of the
manpages. `make release` now builds both architectures via release-windows,
so the windows zips land under the same SHA256SUMS as everything else.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/windows.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/windows.md b/docs/windows.md index 4d01a0d..c1901cd 100644 --- a/docs/windows.md +++ b/docs/windows.md @@ -17,6 +17,12 @@ architectures never share an output directory. The binary appears at `build/win-<arch>/slosh.exe`; copy that to the Windows machine. +For a release, `make -f Makefile.windows ARCH=<arch> dist` stages the same +build as `dist/slosh-<version>-windows-<arch>.zip` — the binary plus the same +licensing paperwork the linux tarballs carry — and `make release` builds both +architectures alongside the linux and macOS artifacts, covered by the same +`SHA256SUMS`. + ## What it does there Everything the POSIX build does: panes, splits, tabs, detachable sessions, the |