Re:When an implementation monoculture might be the right thing
by sanxiyn on Friday June 01, 2018 @12:01AM
(#17202475)
I use many programs compiled with GCC on Windows. MinGW works.
[ Parent
| on HN ]
Re:When an implementation monoculture might be the right thing
by asfasgasg on Friday June 01, 2018 @12:08AM
(#17202500)
I'm sure you can find someone who uses many programs compiled with TCC. That tells me little about the actual prevalence of programs compiled using various compilers.
Re:When an implementation monoculture might be the right thing
by sanxiyn on Friday June 01, 2018 @12:24AM
(#17202542)
I believe NumPy Windows binary is built with MinGW. NumPy is used enough that it is more than "very seldom".
Re:When an implementation monoculture might be the right thing
by filmor on Friday June 01, 2018 @01:34AM
(#17202830)
Python C extensions are (supposed to be) compiled with the same compiler as the Python interpreter you are building against was, which in case of the official python.org release is MSVC, see https://wiki.python.org/moin/WindowsCompilers.
Re:When an implementation monoculture might be the right thing
by tavert on Monday June 04, 2018 @08:01PM
(#17233804)
And that choice of compiler has caused endless headaches for the NumPy and SciPy communities, see e.g. https://github.com/numpy/numpy/wiki/Numerical-software-on-Wi... and https://mingwpy.github.io/motivation.html
VLC's windows binaries are also built with mingw-w64 gcc last I checked, that is likely used even more widely than numpy.