MINGW-packages

> Not sure why the Windows version would be much bigger than the bare metal one. That's probably because there's a bug in the linker, which puts uninitialized variables in the data segment instead of bss. This means unlike the bare metal variant, the Windows executable is full of zeros. This is a well known bug (see https://github.com/msys2/MINGW-packages/issues/18612 for example) which also affects my projects: https://gitlab.com/bztsrc/skandi The Linux CLI version is 216K, the Windows CLI version is 5.4M and the only difference is the lack of bss.

On Nixpkgs master, you can cross compile to MinGW and Cygwin. Native Cygwin builds are also currently in progress: https://github.com/NixOS/nixpkgs/pull/447520. I would expect this to be done very soon, there year even (holidays permitting). There is a MinGW build of Nix but it is missing some features. There has been MSVC build of a fork in the past and I would like to revive that also. There some some open questions relating to Nixpkgs's heavy use of Bash, but longer term I would like to compete for Windows in all ways: - Support all cross (MinGW, Cygwin/MSYS2, MSVC ABI with LLVM, MSVC with Wine) - Be Cygwin packages - Be https://github.com/msys2/MINGW-packages / https://github.com/msys2/MSYS2-packages - Be VCPKG All these things have slightly different trade-offs, and Nixpkgs is very good at portability, so we should simply do them all

Note that MinGW uses libwinpthread, which is known to have slow TLS behavior anyway (I've observed a 100% overhead compared to running the same program under WSL using a linux-native GCC). c.f. https://github.com/msys2/MINGW-packages/discussions/13259

msys2/MINGW-packages: "[Wish] Add 3D library for Python" https://github.com/msys2/MINGW-packages/issues/21325 panda3d/panda3d: https://github.com/panda3d/panda3d Before Steam for Linux, there was tuxmath. tux4kuds/tuxmath//mingw/ has CodeBlocks build config with mingw32 fwics: https://github.com/tux4kids/tuxmath/blob/master/mingw/tuxmat... Code::Blocks: https://en.m.wikipedia.org/wiki/Code::Blocks There's a CMake build: https://github.com/tux4kids/tuxmath/blob/master/CMakeLists.t... But it says the autotools build is still it; configure.ac for autoconf and Makefile.am for automake SDL supports SVG since SDL_image 2.0.2 with IMG_LoadSVG_RW() and since SDL_image 2.6.0 with IMG_LoadSizedSVG_RW: https://wiki.libsdl.org/SDL2_image/IMG_LoadSizedSVG_RW conda-forge has SDL on Win/Mac/Lin. conda-forge/sdl2-feedstock: https://github.com/conda-

Hey, TuxMath is written with SDL, though there's a separate JS port now IIUC. /? mingw: https://github.com/search?q=mingw&type=repositories The msys2/MINGW-packages are PKGBUILD packages: https://github.com/msys2/MINGW-packages : > Package scripts for MinGW-w64 targets to build under MSYS2. > [..., SDL, gles, glfw, egl, glbinding, cargo-c, gtest, cppunit, qt5, gtk4, icu, ki-i18n-qt5, SDL2_pango, jack2, gstreamer, ffmpeg, blender, gegl, gnome-text-editor, gtksourceview, kdiff3, libgit2, libusb, libressl, libsodium, libserialport, libslirp, hugo] PKGBUILD is a bash script packaging spec from Arch, which builds packages with makepkg. msys2/setup-msys2: https://github.com/msys2/setup-msys2: > setup-msys2 is a GitHub Action (GHA) to setup an MSYS2 environment (i.e. MSYS, MINGW32, MINGW64, UCRT64, CLANG32, CLANG64 and/or CLANGARM64 shells) Tho

I find Babun slightly laggy on my system, so my go to tool is Msys2 https://msys2.github.io/ Msys2 is a fork of Cygwin, it does not do away with POSIX emulation, but I find its package management better than Cygwin's. Quite a few packages are supported https://github.com/Alexpux/MSYS2-packages https://github.com/msys2/MINGW-packages