This makes me think that most people don't compile Windows-aware applications in this environment, and instead use one of the other environments. According to Elieux, the -mwin32 option is not really used in the MSYS2 project, so most of these utilities are probably "unaware" that they are running on Windows.Īs of, compile-time errors prevent you from using Microsoft's setupapi.h from this environment. ![]() Most of the utilities provided by MSYS2 were probably compiled using the MSYS2 environment if you run Dependency Walker and look at those utilities, you can see that they depend on msys-2.0.dll. For example, if you wanted to compile the latest version of GNU Grep, you should use the MSYS2 Shell. The MSYS2 Shell is useful for compiling GNU utilities, applications that use advanced features of POSIX, or just generally any application that was not designed with Windows in mind. It doesn't define the _WIN32 preprocessor macro by default, but it will if you provide the -mwin32 options. That DLL is a fork of Cygwin, so it provides good POSIX The executables compiled by gcc in the MSYS2 Shell depend on msys-2.0.dll. In each environment, theĬompiler is invoked by running "gcc". That they each provide a different compiler. The main difference between these environments is The MSYS2 environment actually supports multiple different MSYS2 development environment for WindowsĪs of 2015, the best general purpose development environment for C/C++ programs on Windows seems to be
0 Comments
Leave a Reply. |