Also different people built MinGW with different compilers and/or compiler settings and/or custom patches and/or different libraries included. As JKSH explained, there are at least two main "flavors" of MinGW: The original project and the MinGW-w64 project, both based on GCC/Gygwin and the latter originally forked off from the former. It's OpenSource software, so different forks happen to exist, in parallel. You need to consider that the MinGW doesn't exist.
Mingw get install#
Just include the install folder in the PATH.Īlmost. Additionally, I don't need any environment set up of the host machine. Ok so if I understand correctly, the former contains the compiler plus command line tools, whereas the latter is only the compiler.
Mingw get code#
IIRC, they use the source code from MinGW-w64 MinGW-builds is yet another project, that provides easy-to-use packages for both 32-bit and 64-bit variants of MinGW. The last I heard, MinGW-w64 actually has better support for the Windows API now, compared to. Rather, they've continued developing quite independently. Unfortunately, there seems to be some politics at play, and the 2 projects haven't merged. A fork was created, called MinGW-w64, to create a 64-bit version (although they also develop a 32-bit version). If the Qt Project will consider the former to be the preferred choice, is there a set up specific to it? mingw-get is the package manager (similar to apt-get) for the original MinGW + MSYS toolchain (maintained by ).
It looks like build is not as current as the former. Lukas, what is the difference between the "MinGW-builds": and the "MinGW-get-inst": ? The latter appears to be an installer of the build.
0 kommentar(er)
