undefined | Better HN

0 pointsMayeulC1y ago0 comments

Honestly, given the feedback on the Microsoft site, that makes sense: the redistributable is backwards-compatible, not forward-compatible. Same as with glibc.

IMO, the correct option here is to compile against an older version of the build chain. This is the solution offered by Microsoft, and something you would do on Linux for glibc compatibility as well.

The other option would be to compile without MSVC, using mingw, wine headers, etc.

0 comments

gary_01y ago

> compile without MSVC, using mingw

I believe there are a few open source projects (such as Inkscape[0]) that provide Windows builds this way rather than having to deal with Microsoft's toolchain and runtime. But given its heavy reliance on DirectX APIs and other system libraries, I'm not sure how feasible that route would be for Dolphin.

I do wonder if there would be a performance benefit to compiling with GCC/clang on Windows, as I've seen fairly recent builds of MSVC emit some pretty lousy code in certain cases, and it lacks many of the options that GCC/clang provide, such as an exact equivalent of -fno-math-errno and the like.

[0] https://wiki.inkscape.org/wiki/Compiling_Inkscape_on_Windows

j / k navigate · click thread line to collapse