w64devkit maintainer recaps a year of code-signing, immutable releases, multilib
Nullprogram's retrospective details how co-maintainer Peter0x44 helped add signed, immutable releases and a multilib x64 toolchain to the Windows dev-kit.
What to know
- w64devkit's releases are now code-signed, built via automated GitHub Actions, and made immutable once published.
- The x64 release gained multilib support to also target 32-bit Windows, reducing the need for a separate x86 build in most cases.
- Co-maintainer Peter0x44 drove many of the year's changes, with several improvements contributed back upstream to shared toolchain projects.
- Coverage is limited to the original blog post syndicated across Hacker News, Lobsters, an RSS aggregator, and Mastodon, with almost no independent discussion yet.
w64devkit maintainer Author and lead maintainer of w64devkitPeter0x44 w64devkit co-maintainerMSYS2 Related open-source toolchain project
How it unfolded 1 development · click the chart to see its coverage articlesposts
-
1
Maintainer publishes year-in-review post on w64devkit
The nullprogram.com blog post consolidating these changes was published and cross-posted, surfacing on Hacker News, Lobsters, an HN frontpage RSS feed, and Mastodon the same day.
“Peter0x44 joined as co-maintainer, and has pushed the project in good, new directions, with ideas I would never have considered.”
— w64devkit maintainer, Project maintainer · source -
first by HN Frontpage, 4d ago
-
-
background
w64devkit release packaging becomes code-signed — The maintainer announced in April that all EXEs and DLLs shipped in w64devkit releases are now code-signed with the maintainer's key, reducing false flags from security software.
-
background
GCC patched to allow invocation without PATH setup — A small GCC patch means users no longer need w64devkit's bin/ directory on their PATH to run the compiler, allowing direct invocation from scripts.
-
background
x64 release becomes a multilib toolchain — The x64 build can now also compile 32-bit Windows programs, making the separate x86 release relevant mainly for running on older hardware/OSes; the change was made possible by co-maintainer Peter0x44.
-
background
Release builds automated and locked with GitHub Actions — Builds are now triggered only by the maintainer's tag pushes via GitHub Actions, which code-signs and publishes releases transparently from source, and release immutability was enabled so published artifacts (verified by a release attestation) can never be altered afterward, even by the maintainer.
-
background
MSYS2 adopts the project's aas-sign signing tool — MSYS2 began using the maintainer's signing tool, aas-sign, which is now bundled into w64devkit releases as well.
-
background
Binutils patched to default to bigobj COFF format — A couple of years earlier the maintainer patched Binutils so releases default to the bigobj COFF format, avoiding the 65,535-section limit that large C++ builds can exceed, though this can break interaction with simpler linkers like Go's.