Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Mingw-w64
open-in-new
<h2 id="history">History</h2> <p>In 2005, Mingw-w64 was created by OneVision Software under <a href="/facts/Cleanroom_software_engineering/aUMVIAIH">cleanroom software engineering</a> principles, since the original MinGW project was not prompt on updating its code base, including the inclusion of several key new APIs and also 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.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> It was first submitted to the original MinGW project, but refused under suspicion of using non-public or proprietary information.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a><a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a><a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> For many reasons, the lead developer and co-founder of the MinGW-w64 project, Kai Tietz, decided not to attempt further cooperation with MinGW.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> </p><p>MinGW-w64 provides a more complete Win32 API implementation,<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> including: </p> <ul><li>Better <a href="/facts/C99/o5uMWjTQ">C99</a> support</li> <li><a href="/facts/POSIX_Threads/S8oH6pI9">POSIX Threads</a> (pthreads) support (including the possibility to enable <a href="/facts/C%252B%252B11/fI3YCoKQ">C++11</a> thread-related functionality in GCC's <a href="/facts/Libstdc%252B%252B/A5vQNSAD">libstdc++</a>)</li> <li>GCC multilib, which allows users to install 32-bit and 64-bit libraries in parallel</li> <li><a href="/facts/Unicode_in_Microsoft_Windows/KklG49qq">Unicode</a> entry point (wmain/wWinMain)</li> <li><a href="/facts/Windows_Driver_Kit/RoVIPYox">DDK</a> (from <a href="/facts/ReactOS/BFmfC6BB">ReactOS</a>)</li> <li><a href="/facts/DirectX/jyy75wVN">DirectX</a> (from <a href="/facts/Wine_(software)/JF0wHs7y">Wine</a>)</li> <li><a href="/facts/Large_file_support/sLFofvb7">Large file support</a></li> <li><a href="/facts/Win64/RRw4RtTu">Win64</a> support</li> <li><a href="/facts/Structured_Exception_Handling/oK9Qs8Hr">Structured Exception Handling</a> (SEH) instead of <a href="/facts/DWARF/dRRIGNKS">DWARF</a> or <a href="/facts/Setjmp/c9b2pNrL">sjlj</a> on x86-64 (from gcc 4.8+)</li> <li>Some useful tools such as gendef (an improved version of MinGW's pexports utility), and widl (an <a href="/facts/MIDL/zlqt5sj3">MIDL</a> compiler from Wine).</li></ul> <p>Additionally, the Mingw-w64 project maintains winpthreads, a <a href="/facts/Wrapper_library/b61otW6r">wrapper library</a> 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>. </p> <h2 id="msys2">MSYS2</h2> <p>MSYS2 ("minimal system 2") is a software distribution and a development platform for <a href="/facts/Microsoft_Windows/bwhAhuSL">Microsoft Windows</a>, based on Mingw-w64 and <a href="/facts/Cygwin/0ANCmAgH">Cygwin</a>, that helps to deploy code from the <a href="/facts/Unix/0pNL2seI">Unix</a> world on Windows. It plays the same role the old MSYS did in MinGW.<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a> </p><p>MSYS2 shares this goal of bringing Unix code to Windows machines with several other projects, most notably <a href="/facts/Cygwin/0ANCmAgH">Cygwin</a> and <a href="/facts/Windows_Subsystem_for_Linux/ou97bFN2">Windows Subsystem for Linux</a> (WSL). WSL lets Linux <a href="/facts/Executable_and_Linkable_Format/ro2CYqso">ELF</a> binaries run on Windows through a managed <a href="/facts/Virtual_Machine/BLevU3sx">Virtual Machine</a>. Cygwin provides a full <a href="/facts/POSIX/mQkSt234">POSIX</a> environment (as a windows <a href="/facts/Dynamic-link_library/vySyC1dz">DLL</a>) in which applications, compiled as Windows EXEs, run as they would under Unix.<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a> </p><p>Instead of providing a full environment like Cygwin does, MSYS2 tasks itself with being a development and deployment platform.<a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a> </p> <ul><li>There is a main MSYS2 environment (similar to, and in fact derived from, Cygwin's emulation code) with package manager and standard Unix system tool. 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.</li> <li>In addition, four environments are provided containing 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 environments are MINGW64 and MINGW32 (the original MinGW-w64 environments using gcc, msvcrt, and libstdc++), UCRT64 (adaptation of MINGW64 to ucrt), and CLANG64 (adaptation of UCRT64 to clang and libc++). While Cygwin also provides MinGW-w64 compilers and libraries, the set of available libraries is smaller, and they are not as easily managed due to not being placed in separate prefixes.</li></ul> <p>The main MSYS2 environment provides a <a href="/facts/Package_manager/kEX4kx7g">package manager</a> (<a href="/facts/Pacman_(Arch_Linux)/MTFCkLqH"><i>Pacman</i></a> from <a href="/facts/Arch_Linux/MTFCkLqH">Arch Linux</a>), a <a href="/facts/Bash_shell/RrYLtEJT">bash shell</a>, and other <a href="/facts/Unix/0pNL2seI">Unix</a> programs. It uses a runtime library <i>msys-2.0.dll</i> (~20MB) that is derived from the Cygwin library <i>cygwin1.dll</i>, and is updated regularly to keep track of the Cygwin development. It is intended as a development environment, one that developers can manage (using pacman) and run their tools with. Features judged unnecessary for development are removed.<a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a> </p><p>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.<a class="footnote-ref" id="fnref:11" href="#fn:11"><sup>11</sup></a><a class="footnote-ref" id="fnref:12" href="#fn:12"><sup>12</sup></a> </p><p>MSYS2 and its bash environment is used by <a href="/facts/Git/U5Ty9QmQ">Git</a> and <a href="/facts/GNU_Octave/vVVq5evM">GNU Octave</a> for their official Windows distribution. </p> <h2 id="compiler">Compiler</h2> <p>Most languages supported by GCC are supported on the Mingw-w64 port as well. These include C, <a href="/facts/C%252B%252B/Et0F2qn9">C++</a>, <a href="/facts/Objective-C/5mM557BW">Objective-C</a>, Objective-C++, <a href="/facts/Fortran/m1KqjcMU">Fortran</a>, and <a href="/facts/Ada_(programming_language)/Y2yHel4l">Ada</a>. The GCC runtime libraries are used (libstdc++ for C++, libgfortran for Fortran, etc.). A packaging of <a href="/facts/LLVM/nPmcspQN">LLVM</a>'s clang to mingw-w64 is also provided by MSYS2. It supports ARM for Windows (aarch64-w64-mingw32 and armv7-w64-mingw32).<a class="footnote-ref" id="fnref:13" href="#fn:13"><sup>13</sup></a><a class="footnote-ref" id="fnref:14" href="#fn:14"><sup>14</sup></a> </p><p>Binaries (executables or DLLs) generated with different C++ compilers (like Mingw-w64 GCC and Visual Studio) are in general not link compatible due to the use of different <a href="/facts/Application_Binary_Interface/wc6pmKKb">ABIs</a> and <a href="/facts/Name_mangling/br0AH0zP">name mangling</a> schemes caused by the differences in C++ runtimes. However, compiled C code is link compatible.<a class="footnote-ref" id="fnref:15" href="#fn:15"><sup>15</sup></a> Clang is an exception, as it mostly supports MSVC's C++ ABI on Windows.<a class="footnote-ref" id="fnref:16" href="#fn:16"><sup>16</sup></a> </p><p>The <a href="/facts/Binutils/J44lMK6U">binutils</a> documentation has up-to-date information about its handling of various windows-specific formats and special tools for doing so.<a class="footnote-ref" id="fnref:17" href="#fn:17"><sup>17</sup></a><a class="footnote-ref" id="fnref:18" href="#fn:18"><sup>18</sup></a> </p> <h2 id="external-links">External links</h2> <ul><li><a href="https://www.msys2.org/">MSYS2</a></li> <li><a href="https://winlibs.com">WinLibs</a></li> <li><a href="https://mxe.cc/">MXE</a> - Makefiles to build MinGW on Unix and many common dependencies libraries targeting Win32/64, pre-built packages available</li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>"(MinGW-w64) History". MinGW-w64 Wiki. Archived from the original on 2019-07-05. Retrieved 2016-02-18. <a href="https://sourceforge.net/p/mingw-w64/wiki2/History/" target="_blank">https://sourceforge.net/p/mingw-w64/wiki2/History/</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>Danny Smith (13 August 2007). "Re: Sub project for w64 header & crt". Newsgroup: comp.gnu.mingw.devel. Usenet: 000001c7dd83$9ae74310$fe6d65da@THOMAS. Archived from the original on 23 July 2020. Retrieved 23 July 2020. From a cursory spot check of a few files, the crt sources in particular appear to contain too much undocumented material that I suspect may be derived from proprietary sources. I have since avoided looking at the mingw-w64 sources to avoid any taint of copyright abuse. I could well be wrong, but I would rather be safe than jeopardise the future of the mingw32, which has tried to maintain a "clean-room" ethic during its development. <a href="https://sourceforge.net/p/mingw/mailman/message/10664140/" target="_blank">https://sourceforge.net/p/mingw/mailman/message/10664140/</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>"(MinGW-w64) History". MinGW-w64 Wiki. Archived from the original on 2019-07-05. Retrieved 2016-02-18. <a href="https://sourceforge.net/p/mingw-w64/wiki2/History/" target="_blank">https://sourceforge.net/p/mingw-w64/wiki2/History/</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>Marshall, Keith (19 July 2009). "Re: Harmonizing mingwrt / w32api with mingw-w64". MinGW-dvlpr (Mailing list). Archived from the original on 28 January 2020. Retrieved 12 June 2014. However, we would require a formal audit of mingw-64 code, to ensure conformance with our requirements for truly open documentation of sources, before [merge of mingw-w64] could be completed. <a href="http://sourceforge.net/p/mingw/mailman/message/23100595/" target="_blank">http://sourceforge.net/p/mingw/mailman/message/23100595/</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>Tietz, Kai (20 July 2014). "Re: Harmonizing mingwrt / w32api with mingw-w64". MinGW-dvlpr (Mailing list). Archived from the original on 28 January 2020. Retrieved 12 June 2014. <a href="http://sourceforge.net/p/mingw/mailman/message/23108552/" target="_blank">http://sourceforge.net/p/mingw/mailman/message/23108552/</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>"MinGW-w64". MinGW-w64.org. Archived from the original on 18 October 2019. Retrieved 30 May 2013. <a href="http://mingw-w64.org/" target="_blank">http://mingw-w64.org/</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>"MSYS2". www.msys2.org. Archived from the original on 2021-02-07. Retrieved 2022-09-30. <a href="https://www.msys2.org/" target="_blank">https://www.msys2.org/</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>"ZSH on Windows via MSYS2". 26 July 2018. Archived from the original on 28 January 2020. Retrieved 30 January 2020. <a href="https://medium.com/@borekb/zsh-via-msys2-on-windows-3964a943b1ce" target="_blank">https://medium.com/@borekb/zsh-via-msys2-on-windows-3964a943b1ce</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>"How does MSYS2 differ from Cygwin · msys2/Msys2 Wiki". Archived from the original on 2023-02-15. Retrieved 2023-02-20. <a href="https://www.msys2.org/wiki/How-does-MSYS2-differ-from-Cygwin/" target="_blank">https://www.msys2.org/wiki/How-does-MSYS2-differ-from-Cygwin/</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> <li id="fn:10"><p>"How does MSYS2 differ from Cygwin · msys2/Msys2 Wiki". Archived from the original on 2023-02-15. Retrieved 2023-02-20. <a href="https://www.msys2.org/wiki/How-does-MSYS2-differ-from-Cygwin/" target="_blank">https://www.msys2.org/wiki/How-does-MSYS2-differ-from-Cygwin/</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li> <li id="fn:11"><p>Biswas, Supriyo (2017-04-29). "How to Get an Unix/Linux Environment on Windows with MSYS2". Boolean World. Archived from the original on 2022-09-30. Retrieved 2022-09-30. <a href="https://www.booleanworld.com/get-unix-linux-environment-windows-msys2/" target="_blank">https://www.booleanworld.com/get-unix-linux-environment-windows-msys2/</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></p></li> <li id="fn:12"><p>"How does MSYS2 differ from Cygwin · msys2/Msys2 Wiki". Archived from the original on 2023-02-15. Retrieved 2023-02-20. <a href="https://www.msys2.org/wiki/How-does-MSYS2-differ-from-Cygwin/" target="_blank">https://www.msys2.org/wiki/How-does-MSYS2-differ-from-Cygwin/</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></p></li> <li id="fn:13"><p>"Package: mingw-w64-x86_64-clang". MSYS2 Packages. Archived from the original on 30 October 2020. Retrieved 12 February 2020. <a href="https://packages.msys2.org/package/mingw-w64-x86_64-clang" target="_blank">https://packages.msys2.org/package/mingw-w64-x86_64-clang</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></p></li> <li id="fn:14"><p>Storsjö, Martin (23 April 2020). "mstorsjo/llvm-mingw". GitHub. Archived from the original on 29 November 2020. Retrieved 27 April 2020. <a href="https://github.com/mstorsjo/llvm-mingw" target="_blank">https://github.com/mstorsjo/llvm-mingw</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></p></li> <li id="fn:15"><p>"Interoperability of Libraries Created by Different Compiler Brands". mingw.org. Archived from the original on 2020-11-30. Retrieved 2022-09-30. <a href="https://web.archive.org/web/20201130131120/http://mingw.org/wiki/Interoperability_of_Libraries_Created_by_Different_Compiler_Brands" target="_blank">https://web.archive.org/web/20201130131120/http://mingw.org/wiki/Interoperability_of_Libraries_Created_by_Different_Compiler_Brands</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></p></li> <li id="fn:16"><p>"MSVC compatibility". Clang 11 documentation. Archived from the original on 2021-01-26. Retrieved 2020-02-12. <a href="https://clang.llvm.org/docs/MSVCCompatibility.html" target="_blank">https://clang.llvm.org/docs/MSVCCompatibility.html</a> <a href="#fnref:16" class="footnote-back-ref">↩</a></p></li> <li id="fn:17"><p>"ld: win32". sourceware.org. Archived from the original on 2020-02-14. Retrieved 2020-02-10. <a href="https://sourceware.org/binutils/docs/ld/WIN32.html" target="_blank">https://sourceware.org/binutils/docs/ld/WIN32.html</a> <a href="#fnref:17" class="footnote-back-ref">↩</a></p></li> <li id="fn:18"><p>"GNU Binary Utilities Documentation". sourceware.org. Archived from the original on 2020-02-19. Retrieved 2020-02-10. <a href="https://sourceware.org/binutils/docs/binutils/index.html" target="_blank">https://sourceware.org/binutils/docs/binutils/index.html</a> <a href="#fnref:18" class="footnote-back-ref">↩</a></p></li> </ol>