2 ms·

Are the source code and build instructions used to create these libs available for folks who want to reproduce the standalone artifacts? This reminds me of why

Are the source code and build instructions used to create these libs available for folks who want to reproduce the standalone artifacts? 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. :)

mdaniel 4y ago
I believe it's this: https://github.com/brechtsanders/winlibs_recipes https://github.com/brechtsanders/winlibs_recipes (MIT) combined with https://github.com/brechtsanders/winlibs_tools https://github.com/brechtsanders/winlibs_tools (GPLv2). Although as a drive-by observer, if the quality of those "recipes" (and the idea that one needed to cowboy up some shell scripts to build all that stuff versus using a more formal build system) is any indication, I am for sure not the target audience of this project --- 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/0cf2793e55d410c3f43beb283f63fcb4c352b297.patch 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]`