HOWTO Understanding effects of build directory options on a relocatable MinGW GCC default's paths
1 Summury and purpose of this document
Although there are nor big TODO remaining for this document, some updates are still pending
HOWTO Understanding effects of build directory options on a relocatable MinGW GCC default's paths
Although there are nor big TODO remaining for this document, some updates are still pending
I've noticed that the BinUtils package contains a mingw32/bin directory beside of the bin directory, and the binaraies in mingw32/bin directory are byte-for-byte the same as the ones in bin.
I was curious to understand what this duplication is standing for.
With thanks :)
Yannick - Hibou57
MinGW ("Minimalistic GNU for Windows") is a collection of freely available and freely distributable Windows specific header files and import libraries combined with GNU toolsets that allow one to produce native Windows programs that do not rely on any 3rd-party C runtime DLLs.
In addition to sources maintained directly, and exclusively by ourselves, the MinGW Project makes use of a number of upstream sources, to deliver the package set commonly seen as defining a MinGW installation. This page explains where to find the most up-to-date source code for MinGW packages.
You've identified a bug in a MinGW package, and you've developed a solution to correct the defect. So, how do you submit that solution, for inclusion in MinGW?
All user proposed modifications or enhancements to MinGW are subject to review and approval by the project administrators, and the project development team. By following the guidelines set out below, you will give your solution its best chance of being adopted, in a timely fashion.
For instructions on how to quickly download and install MinGW (including GCC compilers for C, C++, Fortran, Java, and Ada, binutils, Windows API, runtime, and make), please refer to the instructions for Getting Started with MinGW. For more detailed instructions, read HOWTO Install the MinGW GCC Compiler Suite.
Important Note: The build environment described here is used for development of the MSYS product itself; it is not applicable for users who simply wish to use MSYS, as a working environment for developing normal MS-Windows applications, (presumably using MinGW as the compiler suite). The overwhelming majority of MSYS users do not need to set up any such "MSYS Build Environment".
NOTE:
Much of the information presented on this page is obsolete; updated information may be found here.
Pthreads is part of POSIX and Windows isn't a POSIX system. However, there is a third party library on sourceware.org named pthreads-win32. Sourceware.org provides its own lists and MinGW does not support it but you are free to use it with MinGW at your own risk.

Recent comments
15 weeks 5 days ago
15 weeks 6 days ago
17 weeks 2 days ago
17 weeks 5 days ago
18 weeks 1 day ago
20 weeks 3 days ago
26 weeks 1 day ago
26 weeks 2 days ago
29 weeks 4 days ago
32 weeks 1 day ago