Install xwin with Homebrew, Nix

Project links

• Homepage

Commands and aliases

• xwin

Project history

Jake Shadle created the GitHub repository in August 2021 alongside a detailed post on cross-compiling Windows binaries from Linux. The blog explains the practical CI problem: producing `x86_64-pc-windows-msvc` outputs without running the whole Windows toolchain on Windows, while still using clang-cl and lld-link against Microsoft CRT and SDK files.

The README defines xwin's core job as creating CRT and SDK root directories with the includes and libraries needed by native cross-compiling toolchains, including symlinks to repair Windows SDK casing problems on case-sensitive filesystems. The CLI grew commands such as `download`, `unpack`, `splat`, and `minimize`.

Recent releases track changes in Microsoft's installer and manifest ecosystem: channel-name changes, MSI packages without cabinet references, TLS/certificate handling, HTTP retry behavior, and debug-runtime inclusion.

Adoption history

xwin sits in the Rust cross-compilation niche: developers targeting `*-pc-windows-msvc` from Linux or macOS need Windows headers and libraries but often prefer cargo, clang-cl, lld-link, containers, and Linux CI. Packaging xwin in Homebrew, Nix, crates.io, and GitHub releases makes that workflow scriptable.

How it is used

The common flow is `xwin --accept-license splat --output /path/to/sysroot`, then pointing clang-cl, lld-link, Cargo, or build scripts at the produced CRT and SDK include/library directories. `download` and `unpack` expose intermediate steps, while `minimize` can trace a Cargo build and produce a reduced map of files actually used.

Why package nerds care

xwin is significant because it turns proprietary-platform SDK acquisition into a reproducible package-style operation without redistributing Microsoft's files. It collapses a painful cross-compilation prerequisite into one auditable CLI.

It also captures a modern packaging pattern: acquiring upstream binary installer payloads, normalizing layout, fixing filesystem case mismatches, caching aggressively, and producing a sysroot other tools can consume.

Timeline

• 2021-08-04: GitHub repository created.
• 2021-08-22: Shadle publishes the cross-compiling Windows binaries from Linux walkthrough describing the new utility and its CI motivation.
• 2021: README-era workflow centers on downloading CRT/SDK payloads and `splat` output for clang/LLVM Windows cross builds.
• 2024-2025: Releases focus on Microsoft installer churn, HTTP/TLS behavior, debug-runtime support, and SDK package layout changes.
• 2026-04-20: 0.9.0 release fixes channel-name handling for newer Microsoft manifest versions.

Related projects

• clang-cl, lld-link, and LLVM: the non-Windows toolchain xwin is designed to feed.
• Rust target `x86_64-pc-windows-msvc`: a primary driver for xwin's documented workflow.
• cargo and cc-rs: common Rust build tooling that consumes compiler/linker configuration pointing at xwin output.
• winsysroot: a layout style xwin can generate for clang-cl-oriented SDK discovery.

Sources

• https://api.github.com/repos/Jake-Shadle/xwin
• https://api.github.com/repos/Jake-Shadle/xwin/releases?per_page=8
• https://crates.io/crates/xwin
• https://github.com/Jake-Shadle/xwin
• https://jake-shadle.github.io/xwin/
• https://raw.githubusercontent.com/Jake-Shadle/xwin/main/README.md