Mingw-w64

In 2005, Mingw-w64 was created by OneVision Software under clean room design principles, since the original MinGW project was not prompt on updating its code base, including the inclusion of several key new APIs and the much needed 64-bit support. In 2008, OneVision then donated the code to Kai Tietz, one of its lead developers, under the condition that it remain open source.[2] It was first submitted to the original MinGW project, but refused under suspicion of using non-public or proprietary information.[3] For many reasons, the lead developer and co-founder of the MinGW-w64 project, Kai Tietz, decided not to attempt further cooperation with MinGW.[4]

MinGW-w64 provides a more complete Win32 API implementation,[5] including:

• better C99 support
• POSIX Threads (pthreads) support (including the possibility to enable C++11 thread-related functionality in GCC's libstdc++)
• GCC multilib, which allows users to install 32-bit and 64-bit libraries in parallel
• Unicode entry point (wmain/wWinMain)
• DDK (from ReactOS)
• DirectX (from Wine)
• Large file support
• Win64 support
• Structured Exception Handling (SEH) instead of DWARF or sjlj on x86-64 (from gcc 4.8+)
• Some useful tools such as gendef (an improved version of MinGW's pexports utility), and widl (an MIDL compiler from Wine).

Additionally, the Mingw-w64 project maintains winpthreads, a wrapper library similar to pthreads-win32, with the main difference that it allows GCC to use it as a threads library resulting in functional C++11 thread libraries <thread>, <future>, and <mutex>.

MSYS2 ("minimal system 2") is a software distribution and a development platform for Microsoft Windows, based on Mingw-w64 and Cygwin, that helps to deploy code from the Unix world on Windows.[6]

MSYS2 shares this goal of bringing Unix code to Windows machines with several other projects, most notably Cygwin and Windows Subsystem for Linux (WSL). WSL lets Linux ELF binaries run on Windows, with limited support for kernel calls and significant limitations in graphical applications. Cygwin provides a full POSIX environment (as a windows DLL) in which applications, compiled as Windows EXEs, run as they would under Unix.[7]

Instead of providing a full environment like Cygwin does, MSYS2 tasks itself with being a development and deployment platform.[8] MSYS2 installs 3 sets of environments, each with a separate set of programs and libraries. Two of them, called 32-bit MinGW-w64 and 64-bit MinGW-w64, are simply composed of native compilers, build tools and libraries that can be directly used to build native Windows 32-bit or 64-bit programs. The final programs built with the two native environments don't use any kind of emulation and can run or be distributed like native Windows programs. The third environment installed, called MSYS2, instead provides an emulated POSIX environment, like Cygwin, with a package manager and standard Unix system tools. This way, when managing MSYS2 itself, standard Unix tools can be used unmodified by using the emulated environment. It's also possible to install build tools in the MSYS2 emulated environment in case the user wants to build software that depends on the POSIX emulation layer instead of the native API.

The main MSYS2 environment provides a package manager (Pacman from Arch Linux), a bash shell, and other Unix programs. It uses a runtime library msys-2.0.dll (~20MB) that is derived from the Cygwin library cygwin1.dll, and is updated regularly to keep track of the Cygwin development. It is intended as a development environment, one that developers can manager (using pacman) and run their tools with. Features judged unnecessary for development are removed.[8]

As with Cygwin, MSYS2 supports path translation for non-MSYS2 software launched from it. For example one can use the command notepad++ /c/Users/John/file.txt to launch an editor that will open the file with the Windows path C:\Users\John\file.txt.[9][8]

MSYS2 and its bash environment is used by Git and GNU Octave for their official Windows distribution.

Most languages supported by GCC are supported on the Mingw-w64 port as well. These include C, C++, Objective-C, Objective-C++, Fortran, and Ada. The GCC runtime libraries are used (libstdc++ for C++, libgfortran for Fortran, etc.). A packaging of LLVM's clang to mingw-w64 is also provided by MSYS2. It supports ARM for Windows (aarch64-w64-mingw32 and armv7-w64-mingw32).[10][11]

Binaries (executables or DLLs) generated with different C++ compilers (like Mindw-w64 GCC and Visual Studio) are in general not link compatible due to the use of different ABIs and name mangling schemes caused by the differences in C++ runtimes. However, compiled C code is link compatible.[12] Clang is an exception, as it mostly supports MSVC's C++ ABI on Windows.[13]

The binutils documentation has up-to-date information about its handling of various windows-specific formats and special tools for doing so.[14][15]

• official website