WinLibs: Standalone build of GCC and MinGW-w64 for Windows
winlibs.com
winlibs.com
After digging through some of the sublinks:
- You can run gcc in the Command Prompt without using a special shell (MSYS2 has its own shell launcher)
- Maybe MSYS2’s gcc handles exceptions (SEH, etc.) differently
- Lacks a package manager like MSYS2’s pacman (which comes from Arch Linux). But winlibs plans to have something in the future
What did I miss? Would love to see a comparison directly on the home page.
Given how sparse the C standard library is and how much effort went into/goes into mingw, Cygwin, msys2, and co; you’d assume they would just use the native Win32 APIs and supplement with unversioned/undocumented plain MSVCRT.DLL that is always available on all versions of Windows [0].
This reminds me of why I stopped trying to compile C++ stuff on windows; there are too many incompatible series of MSVC and project compilation can be a major undertaking.
Maven + JDK and Golang build systems aren't perfect, but they tend to be predictable and have worked out a lot better for me across many dimensions. :)
---
I also had no idea one could have "No commit message" since git has always given me the finger:
$ git commit --allow-empty -F/dev/null
Aborting commit due to empty commit message.
Looking at the commit <https://github.com/brechtsanders/winlibs_recipes/commit/0cf2...> I'm guessing it may be some `git am` trickery at work since `git am` does cheerfully apply apply the commit if the subject line is just `[PATCH]`