Search results
Aug 30, 2014 · MinGW-w64 only provides their source code, but no binaries to "just use" the compiler. MinGW-builds is a somewhat separate project to provide binaries in the most useful configurations. To get a specialized build of MinGW-w64, manual compiling is still possible.
Mingw-w64 can be run natively on Microsoft Windows, cross-hosted on Linux (or other Unix), or "cross-native" on MSYS2 or Cygwin. Mingw-w64 can generate 32-bit and 64-bit executables for x86 under the target names i686-w64-mingw32 and x86_64-w64-mingw32.
Although programs produced under MinGW are 32-bit executables, they can be used both in 32 and 64-bit versions of Windows. The development of the MinGW project has been forked with the creation in 2005–2008 of an alternative project called Mingw-w64.
For mingw, you want to download and install MSYS2. Using the builtin terminal, search for gcc pacman -Ss gcc. You can install gcc for "mingw32", "mingw64", or "ucrt64"; I always use "ucrt64" pacman -S ucrt64/mingw-w64-ucrt-x86_64-gcc.
Standalone MinGW-w64+GCC builds for Windows, built from scratch (including all dependencies) natively on Windows for Windows. Downloads are archive files (.zip or .7z). No installation is required, just extract the archive and start using the programs in mingw32\bin or mingw64\bin.
It builds a cross compiler and a large selection of platform independent libraries (like boost, QT, and lots of less notable libraries). With MXE, boost becomes a lot more attractive as a solution. I've used MXE to build a project that depends on Qt, boost, and libexiv2 with nearly no trouble.
Oct 18, 2017 · GCC build by mingw-builds and MSYS2 are build with different configurations, and bundled with different reversion of MinGW-w64 headers/libs. One difference: mingw-builds prefer to static link GCC self's dependecy libs (zlib, gmp, mpfr, mpc, isl, ...), while MSYS2 prefer to dynamic link them.
