molto 0.41.0

Linux

Static x86-64 binary. No glibc requirement, nothing to unpack.

base=https://github.com/moltobuild/molto/releases/download/v0.41.0
curl -fsSLO $base/molto-0.41.0-x86_64-linux
curl -fsSLO $base/SHA256SUMS
sha256sum --check --ignore-missing SHA256SUMS
chmod +x molto-0.41.0-x86_64-linux
sudo install molto-0.41.0-x86_64-linux /usr/local/bin/molto

Windows

molto-0.41.0-x86_64-windows.exe, x86-64, Windows 10 or later.
Statically linked against UCRT: there is nothing to put beside it.

Windows is not a supported platform yet, and this binary does not
claim it is. RFC-0017 sets four bars for that word and the fourth —
the full suite green on a Windows runner — is not met. What is
measured to work, in CI, on a Windows runner, every push:

• new, build and run on a project, which is also asserted
  against this exact binary before it is published
• molto building molto with molto

Install it with PowerShell. Get-FileHash and Invoke-WebRequest
are built in, so there is nothing to install in order to install it:

$base = "https://github.com/moltobuild/molto/releases/download/v0.41.0"
$exe  = "molto-0.41.0-x86_64-windows.exe"
$dir  = "$env:LOCALAPPDATA\Programs\molto"

New-Item -ItemType Directory -Force -Path $dir | Out-Null
Invoke-WebRequest "$base/$exe" -OutFile "$dir\molto.exe"
Invoke-WebRequest "$base/SHA256SUMS" -OutFile "$env:TEMP\SHA256SUMS"

# The sums file names the file it covers, so check against that line.
$want = (Select-String -Path "$env:TEMP\SHA256SUMS" -Pattern $exe).Line.Split()[0]
$got  = (Get-FileHash "$dir\molto.exe" -Algorithm SHA256).Hash.ToLower()
if ($want -ne $got) { throw "checksum mismatch" }

# On PATH for this user, for every shell after this one.
[Environment]::SetEnvironmentVariable(
    "Path", [Environment]::GetEnvironmentVariable("Path", "User") + ";$dir", "User")

Open a new terminal, then molto new hello and molto run.

What is known not to: molto's own test suite does not finish there.
The state of the port is the Windows badge on the README, and it is
red on purpose until it isn't.

Choosing a compiler

Molto does not choose one, it asks pickup. Install that
and molto finds a toolchain by itself; without it, name one by hand:

export C_COMPILER=gcc CPP_COMPILER=g++

Without either, new, init, add, remove and metadata work, and
build, test, fmt and lint report that no compiler was resolved.

molto-0.41.0.cdx.json is molto's own CycloneDX bill of materials.

What's Changed

• The macOS port: measured, then the first tranche by @black-redoc in #67

Full Changelog: v0.40.0...v0.41.0