mingw-w64

GCC for Windows 64 & 32 bits

Mingw-w64

Mingw-w64 is an advancement of the original mingw.org project, created to support the GCC compiler on Windows systems. It has forked it in 2007 in order to provide support for 64 bits and new APIs. It has since then gained widespread use and distribution.

The development and community are very active and welcoming with new contributors every month and simple installers.

Version 5 has been released

v5.0.3: 2017-11-04

initial Release: 2016-10-19

  • Fixes to the __mingw_printf family of functions.
  • DirectX updates from Wine.
  • Various updates to support Windows 7 and 10.
  • Various header typo fixes.

You can also look at the full list of versions.

Headers, Libraries and Runtime

  • More than a million lines of headers are provided, not counting generated ones, and regularly expanded to track new Windows APIs.
  • Everything needed for linking and running your code on Windows.
  • Winpthreads, a pthreads library for C++11 threading support and simple integration with existing project.
  • Winstorecompat, a work-in-progress convenience library that eases conformance with the Windows Store.
  • Better-conforming and faster math support compared to Visual Studio's.

Tools

  • gendef: generate Visual Studio .def files from .dll files.
  • genidl: generate .idl files from .dll files.
  • widl: compile .idl files.

Friend projects

Mingw-w64 interacts a lot with other projects in order to help everyone move forward. Contributions have been going to and coming from these projects:

Most Recent Activity

Baykalov Pyotr modified a comment on ticket #704
19.02.2018

The command itself (present in logs): x86_64-w64-mingw32-objcopy --only-keep-debug debug/sweepToolV1.exe debug/sweepToolV1.exe.debug from standalone MinGW It's w64 of course. I used Cygwin's MinGW for backtrace because of easily accessible debug info, the same problem happens with standalone MinGW w64 (GCC 5.4.0, binutils 2.25). It seems to be specific to x86-64 binutils.

Baykalov Pyotr modified a comment on ticket #704
19.02.2018

The command itself (present in logs): x86_64-w64-mingw32-objcopy --only-keep-debug debug/sweepToolV1.exe debug/sweepToolV1.exe.debug from standalone MinGW It's w64 of course. I used Cygwin's MinGW for backtrace because of easily accessible debug info, the same problem happens with standalone MinGW w64 (GCC 5.4.0, binutils 2.25). It seems to be specific to x86-64.

Baykalov Pyotr modified a comment on ticket #704
19.02.2018

The command itself (present in logs): x86_64-w64-mingw32-objcopy --only-keep-debug debug/sweepToolV1.exe debug/sweepToolV1.exe.debug from standalone MinGW It's w64 of course. I used Cygwin's MinGW for backtrace because of easily accessible debug info, the same problem happens with standalone MinGW w64 (GCC 5.4.0, binutils 2.25).

Baykalov Pyotr modified a comment on ticket #704
19.02.2018

The command itself (present in logs): x86_64-w64-mingw32-objcopy --only-keep-debug debug/sweepToolV1.exe debug/sweepToolV1.exe.debug

Baykalov Pyotr posted a comment on ticket #704
19.02.2018

The command itself (present in logs): x86_64-w64-mingw32-objcopy --only-keep-debug debug/sweepToolV1.exe debug/sweepToolV1.exe.debug

Baykalov Pyotr created ticket #704
19.02.2018

objcopy crash

Demyan Kimitsa posted a comment on ticket #693
19.02.2018

Sure, background info from http://www.cygwin.com/cygwin-ug-net/using-textbinary.html On a UNIX system, when an application reads from a file it gets exactly what's in the file on disk and the converse is true for writing. The situation is different in the DOS/Windows world where a file can be opened in one of two modes, binary or text. In the binary mode the system behaves exactly as in UNIX. However on writing in text mode, a NL (\n, ^J) is transformed into the sequence CR (\r, ^M) NL. In other...

Martin Storsjö committed [409500]
18.02.2018

msvcrt: Remove "DATA" attributes for _onexit for i386

NightStrike posted a comment on ticket #697
18.02.2018

What link are you trying to use?

NightStrike posted a comment on ticket #693
18.02.2018

Do you have a test case to demonstrte the problem, or a proposed patch to fix?