David Grayson <davidegray...@gmail.com> writes: > No, the MSYS2 MinGW make packages do not supply a "make.exe". That would > cause lots of compatibility problems and break a lot of packages because of > the bugs and quirks in MinGW make. > > $ pacman -Ql mingw-w64-i686-make > mingw-w64-i686-make /mingw32/ > mingw-w64-i686-make /mingw32/bin/ > mingw-w64-i686-make /mingw32/bin/mingw32-make.exe
Oh, yes, forgot about that. I stopped using make long time ago. Then try executing mingw32-make.exe instead of make.exe. > mingw-w64-i686-make /mingw32/include/ > mingw-w64-i686-make /mingw32/include/gnumake.h > mingw-w64-i686-make /mingw32/lib/ > > You might modify the Makefile to convert the path using the cygpath > utility, doing something like: > > echo "#include \"$(shell cygpath -w $<)\"" > $@ That's another possibility, yes, but requires patching a generated file. You can also modify __pch.h directly after the error and re-run make. > LH_Mouse will probably have a better suggestion, and it looks like you > already asked him on GitHub: https://github.com/lhmouse/mcfgthread/issues/25 It would be nice if LH_Mouse could clarify the specific setup required for building his project. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Msys2-users mailing list Msys2-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/msys2-users
