diff options
| author | Peter Geissler <peter@haxx.in> | 2026-08-28 14:22:57 +0200 |
|---|---|---|
| committer | Peter Geissler <peter@haxx.in> | 2026-08-28 14:22:57 +0200 |
| commit | 7941820413d82b3d62d7fc2ac15ef0e1b3b69ee4 (patch) | |
| tree | 8f5cf4a5614f9b5af86a4c5a230e48469d0a54d8 /include | |
| parent | windows: fall back to `edit`, not to a notepad window (diff) | |
| download | slosh-7941820413d82b3d62d7fc2ac15ef0e1b3b69ee4.tar.gz slosh-7941820413d82b3d62d7fc2ac15ef0e1b3b69ee4.tar.xz slosh-7941820413d82b3d62d7fc2ac15ef0e1b3b69ee4.zip | |
docs: the Windows build is a cross-compile, and only that
The docs offered a native build as an equal alternative -- "the same
command builds natively on the Windows box itself, with zig on PATH and
a make" -- and it does not work. Makefile.windows needs sed, cat,
mkdir -p and shell grouping, none of which cmd.exe has; and on ARM64
`zig cc` in zig 0.16.0 dies with an access violation on a one-line C
file, so the compiler cannot run there at all. The zip that does it
matches the published shasum, so this is upstream rather than a bad
download.
Nobody following those two sentences reached a binary. So they are
gone, along with the "# host arch, native" usage line in the makefile
and the "cross-compiles too" aside in the two install sections, which
both implied that building on the box was the normal path and the
cross-compile a bonus. It is the other way round, and now the pages
say so once, in the same words each time.
`builds and runs natively` on the doc's first line loses `builds`:
what is native about slosh.exe is the binary, not where it was made.
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions
