I’m using Mingw to build a C/C++ project. This project has makefiles beyond my comprehension, and relies on a custom and quite sophisticated toolchain to compile it. It’s quite convenient to have GNU tools available on Windows, especially from Windows’s cmd shell, but while invoking the tools (make in particular), MinGW seems to change my PATH around.
Cmd does it normally:
echo %PATH% > ... c:\Apps\msys\bin ... (from cmd)
but msys changes this address to :
echo $PATH > ... /usr/bin ...
in msys, even when I print the PATH from a makefile. As a result, make complains that it can’t find commands like make, uname, echo, you name it (no pun intended).
Strangely, I managed to get this environment working ages ago without a hitch, but this is the first time I remember seeing this path problem. How can I get MinGW/msys to correctly point to its executables?
richard has a point – there were two different shells fighting over environment variables (not to mention running msys) and so each parsed its own and the system’s environment variables differently.
Also make sure that variables defined in your user or system environment are properly written – Windows likes “C:\foo\bar” style paths, but Msys treats them as “/c/foo/bar”.