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.2: 2017-03-28

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

Zufu Liu posted a comment on discussion Open Discussion
17.10.2017

The thread model is "posix", please look at https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-gcc/PKGBUILD Which says: On line 85 (https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-gcc/PKGBUILD#L85) _threads="posix" On line 157 (https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-gcc/PKGBUILD#L157) case "${CARCH}" in i686) local _conf="--disable-sjlj-exceptions --with-dwarf2" LDFLAGS+=" -Wl,--large-address-aware" local _arch=i686 ;; x86_64) local _arch=x86-64...

Zufu Liu posted a comment on discussion Open Discussion
17.10.2017

This can be chekced by using gcc -v or g++ -v command. Threading model: posix (this not checked by myself, but since it's Linux like environment.). Exception implementation for i686 is dw2 (same as old MinGW, i686 Cygwin), for x86_64 it's seh (same as x86_64 Cygwin). This can be checked without install gcc: $ pacman -Fy $ pacman -Fl mingw-w64-i686-gcc-libs | grep libgcc mingw-w64-i686-gcc-libs mingw32/bin/libgcc_s_dw2-1.dll $ pacman -Fl mingw-w64-x86_64-gcc-libs | grep libgcc mingw-w64-x86_64-gcc-libs...

Youda posted a comment on discussion Open Discussion
16.10.2017

Hi. I would like to use the compiler gcc, g++ and other build tools on Windows. But i can't decide between those provided by Mingw-builds and the packages in Msys2. I like the Msys2 project because of the terminal, bash and ability to install other typical Linux tools, but it seems Mingw-builds offer more options when installing the compiler, some of which i would preffer over the others. So what exactly are the differences between the toolchain from Mingw-builds installer or archive the toolchain...

Doug Semler posted a comment on ticket #40
13.10.2017

Oh aside...the way you described it, your definition isn't on the stack. Since it sounds like a multiply defined symbol it's probably in the readonly data

Doug Semler modified ticket #40
13.10.2017

why are you breaking my code specifically?

Doug Semler posted a comment on ticket #40
13.10.2017

Yes. We explicitly made it so your "code" would fail. Or you can look up what const storage specifiers mean. And scope rules. You aren't a programmer are you? If you are please tell me the company you work for so i can avoid all of the "commercial code" they produce (Invalid isn't valid choice so next best thing)

Jim Michaels modified a comment on ticket #40
13.10.2017

why is the compiler trying to link a const int? you should have to define it in 2 places, the header and the .cpp file, and not as extern, that used to throw an error. why not now? is that in the spec? no a const is just a value you get off the stack.

Jim Michaels modified a comment on ticket #40
13.10.2017

why is the compiler trying to link a const int? you should have to define it in 2 places, the header and the .cpp file, and not as extern, that used to throw an error. why not now? is that in the spec?

Jim Michaels posted a comment on ticket #40
13.10.2017

why is the compiler trying to link a const int?

Jim Michaels posted a comment on ticket #40
13.10.2017

and by the way, 32-bit has 2x the problem 64-bit does now... I would suppose the error server is still grinding out garbage.