This is an old revision of the document!
Mingw-w64 brings free software toolchains to Windows. It hosts a vibrant community which builds and debugs software for Windows while providing development environment for everyone to use.
It has forked mingw.org in order to move forward and provide 64bit support and support for new APIs and has brought countless improvements since its creation in 2007.
Website is evolving. The website is changing; please forgive us for a small lack of polishing for a few days and please report issues you encounter.
More than a million lines of headers are already there and the count is continuously increasing to stay up-to-date with new versions of Windows.
Mingw-w64 is not a compiler project but a project used with compilers. Of course, for simplicity, many pre-packaged toolchains are available in the Downloads section and several of them come with additional libraries and tools for extra convenience.
All the additional libraries needed to link your code and run it directly on Windows are provided along with libraries like winpthreads which provides support for C++11 threading and winstorecompat, a work-in-progress convenience library to ease conformance with the Windows Store.
In addition to the usual compilers, linkers and debuggers from the toolchain, mingw-w64 provides gendef to generate Visual Studio .def files from a .dll, genidl to generate .idl files from a .dll and widl to compile them.
Version 2.0 focused on expanding Windows Vista/7 API support.
widl: Allow overriding the default include path
widl: Regenerate Makefile.in and configure
include/winioctl.h: Add new device types.
Dear Kai, Thanks for the reply and I agree with what you wrote. Best regards, HEMMI, Shigeru
Hi, well, any fortran application needs libgfortran runtime. Therefore I assume that fortran library is linked statically here. No idea why that happend, but it seems to me the most obvious cause. Regards, Kai Am Di., 25. Sep. 2018 um 06:41 Uhr schrieb HEMMI, Shigeru email@example.com: An executable program, MySomeExe.exe is built from some forran(+C) source files with the x86_64-8.1.0 mingw-w64 tool. I examined shared library dependencies by dumpbin command of MS. The output is...
Ok. I usually install mingw-w64 via the installer mingw-w64-install.exe available at https://sourceforge.net/projects/mingw-w64/files/ . On this same link I usually check if a new compiler version has become available (but it's not clear if the same compiler has been re-released) So, who should I ask to, or on what other url should I check ? Is there a list of these toolchain providers ? Thanks, Marco
We don't dictate toolchain release schedules, you can always ask the providers themselves.
winerror.h: Add error codes in range 740-807