3 ms·

have you guys considered mingw? It never seems like mingw gets any love in the real world.

jlarocco 14y ago
In my experience, using Mingw in the real world is a mess. It doesn't play nicely with MSVC++, which is a big problem because most third party libraries on Windows are built with MSVC++ and expect projects using them to be built with MSVC++. And the only debugger usable with Mingw is raw GDB. The debug format it uses isn't compatible with MSVC++'s debugger. Sure, GDB is very powerful, but it's very difficult to use compared to MSVC++, XCode, and even the GDB front ends on Linux. Also, there's not much of a build system with Mingw unless you're happy with hand rolled Makefiles or using MSYS. I've never had much luck running MSYS. Maybe it's improved lately, but downloading an arbitrary open source library and trying to run "./configure && make" in MSYS is a crap shoot. Unless the library author has taken steps to make it work it probably won't. As somebody else said, if you're porting code from Linux that uses a lot of non-standard GCC extensions, GNU Make and autotools then Mingw is tolerable as long as you can develop entirely on Linux and only use MingW for porting and testing. There are some limited cases where it's actually pretty good, though. For example, the open source version of Qt ships its own version of GCC, GNU Make, etc, and hides the details behind their Qt Creator IDE. If you're using Qt with minimal dependencies outside of Qt, it's a nice setup. Also, GHC and the Ruby "Windows dev kit" do the same thing for compiling/building language extensions.
ahelwer 14y ago
I don't know, I tried to use mingw to get hwloc to compile. That was one of the more unpleasant experiences in my dev career.
pkmays 14y ago
Unlike ICC, MinGW's gcc.exe is not a drop in replacement for cl.exe. It's a separate compilation environment. The headers are different and often out of date compared to the Windows SDK. Microsoft extensions are not supported so it chokes on newer APIs like DirectX 11. If you are a Mac or Linux weenie who just wants to port something over to Windows sure, no problem, use MinGW. But good luck getting any Visual Studio devs to rely on what is, for all intents and purposes, a second rate Win32 toolchain.

In my experience, using Mingw in the real world is a mess. It doesn't play nicely with MSVC++, which is a big problem because most third party libraries on Windows are built with MSVC++ and expect projects using them to be built with MSVC++. And the only debugger usable with Mingw is raw GDB. The debug format it uses isn't compatible with MSVC++'s debugger. Sure, GDB is very powerful, but it's very difficult to use compared to MSVC++, XCode, and even the GDB front ends on Linux. Also, there's not much of a build system with Mingw unless you're happy with hand rolled Makefiles or using MSYS. I've never had much luck running MSYS. Maybe it's improved lately, but downloading an arbitrary open source library and trying to run "./configure && make" in MSYS is a crap shoot. Unless the library author has taken steps to make it work it probably won't. As somebody else said, if you're porting code from Linux that uses a lot of non-standard GCC extensions, GNU Make and autotools then Mingw is tolerable as long as you can develop entirely on Linux and only use MingW for porting and testing. There are some limited cases where it's actually pretty good, though. For example, the open source version of Qt ships its own version of GCC, GNU Make, etc, and hides the details behind their Qt Creator IDE. If you're using Qt with minimal dependencies outside of Qt, it's a nice setup. Also, GHC and the Ruby "Windows dev kit" do the same thing for compiling/building language extensions.

ahelwer 14y ago

I don't know, I tried to use mingw to get hwloc to compile. That was one of the more unpleasant experiences in my dev career.

pkmays 14y ago

Unlike ICC, MinGW's gcc.exe is not a drop in replacement for cl.exe. It's a separate compilation environment. The headers are different and often out of date compared to the Windows SDK. Microsoft extensions are not supported so it chokes on newer APIs like DirectX 11. If you are a Mac or Linux weenie who just wants to port something over to Windows sure, no problem, use MinGW. But good luck getting any Visual Studio devs to rely on what is, for all intents and purposes, a second rate Win32 toolchain.