Because cross-compiling binaries for Windows is easier than building natively

This page summarizes the projects mentioned and recommended in the original post on

Our great sponsors
  • Sonar - Free webinar: The Power of Clean C++
  • Scout APM - Truly a developer’s best friend
  • InfluxDB - Build time-series-based applications quickly and at scale.
  • Zigi - The context switching struggle is real
  • glibc_version_header

    Build portable Linux binaries without using an ancient distro

    There are other approaches like or sysroots with older glibc, e.g. - you don't need your whole XP, just the the system libs to link against.

    Sure, having a nice SDK where you can just specify the minimum vesion you want to support would be nice but who do you expect to develop such an SDK? GNU/glibc maintainers? They would rather you ship as source. Red Hat / SUSE / Canonical? They want you to target only their distro. Valve? They decided its easier to just provide an unchaning set of libraries since they need to support existing games that got things wrong anyway and already have a distribution platform to distribute such a base system along with the games without bundling it into every single one.

  • mach

    Mach is a game engine & graphics toolkit for the future.

    * Linux (arm): 15 MiB

    That's full cross compilation of WebGPU GUI applications to all desktop platforms in under ~217 MiB for most platforms.


  • Sonar

    Free webinar: The Power of Clean C++. Are you ready to take your C++ code to the next level? Join Sonar on December 7th for our live webinar as we discuss how to get your code clean - and stay clean - with minimal effort and without being overloaded with warnings. Register now!

  • project-azua

    Data Efficient Decision Making

  • xwin

    A utility for downloading and packaging the Microsoft CRT headers and libraries, and Windows SDK headers and libraries needed for compiling and linking programs targeting Windows.

    There's tooling that mostly avoids this.

    This is a utility that fixes a lot of the cross-compiling issues for windows by giving you a portable, unfucked naming, and not-massive SDK. It's the same SDK you get when you install MSVC but it's only a few hundred megs and the names are consistent even with all of Windows' fucked up tooling.

    The only caveat is you need to provide your own compiler, in this case clang is often the best option.

  • winget-cli

    Windows Package Manager CLI (aka winget)

  • zig

    General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.

    I was sad to find out "Zig supports only the last three macOS versions". No ncdu2 for me :(

  • WSL

    Issues found on WSL

    This one? I remember it as an earnest description of the difficulties the WSL team had with the speed of NTFS - and I think it was one of the reasons for the switch to virtualisation in WSL2.


  • Scout APM

    Truly a developer’s best friend. Scout APM is great for developers who want to find and fix performance issues in their applications. With Scout, we'll take care of the bugs so you can focus on building great things 🚀.

  • llvm-mingw

    An LLVM/Clang/LLD based mingw-w64 toolchain

    Sadly Qt ships MinGW 8.1 which is positively ancient (released in 2018). If you're starting a new project (which you likely are if you are installing an IDE aha) there's no reason not to go for more recent compilers - msys2 has GCC12 ( and Clang 14 ( which just work better overall, have much more complete C++20 support, have less bugs, better compile times (especially clang with the various PCH options that appeared in the last few versions), better static analysis, etc.

    Personally I use's releases directly which does not require MSYS but that's because I recompile all my libraries with specific options - if the MSYS libs as they are built are good for you there's no reason not to use them.

  • mxe

    MXE (M cross environment)

    I used to use MXE [1] to compile fully static Windows binaries on Linux VMs hosted with Travis. It needed to crane in everything though, so it was a source of bottlenecks from time to time. I was also uncertain about the provenance of a lot of the dependencies in that toolchain. So when Travis died I took the opportunity to move Windows builds back to gnu with msys2, all over GH Actions. These are actually comparatively snappy and I’m reasonably satisfied with it.


  • BinaryBuilder.jl

    Binary Dependency Builder for Julia

    There is the Julia package which creates an environment that fakes being another, but with the correct compilers and SDKs . It's used to build all the binary dependencies

  • osxcross

    Mac OS X cross toolchain for Linux, FreeBSD, OpenBSD and Android (Termux)

  • manylinux

    Python wheels that work on any linux (almost)

    It's very hard. Incompatible glibc ABIs make this nigh impossible, there's a reason Steam installs a vcredistributable.dll for pretty much every game on Windows.

    Look no further than the hoops you need jump through to distribute a Linux binary on PyPI [1]. Despite tons of engineering effort, and tons of hoop jumping from packagers, getting a non-trivial binary to run across all distros is still considered functionally impossible.


  • cygwin-rurban

    Automatically exported from

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts