From: Marcus G. <mar...@ho...> - 2002-08-02 19:10:41
|
I have a problem with the MinGW make program: Under Windows 2000 the $(MAKE) variable is "make", which is what I want, but under Windows 98 the $(MAKE) variable is the full path, with FORWARD slashes. In other words, this Makefile: default: @echo $(MAKE) ...results in: C:/COMMAND/MINGW32/BIN/MAKE.EXE (on my system) Needless to say, it is impossible to use the $(MAKE) variable for executing the make program :( Using the full path would be OK, but why convert back slashes to forward slashes? Is this Cygwin heritage or something? /Marcus |
From: Luke D. <cod...@ho...> - 2002-08-03 06:05:32
|
----- Original Message ----- From: "Marcus Geelnard" <mar...@ho...> To: "Mingw-users" <min...@li...> Sent: Saturday, August 03, 2002 3:13 AM Subject: [Mingw-users] make bug (Win98) > I have a problem with the MinGW make program: > > Under Windows 2000 the $(MAKE) variable is "make", which is what I > want, but under Windows 98 the $(MAKE) variable is the full path, > with FORWARD slashes. In other words, this Makefile: > > default: > @echo $(MAKE) > > ...results in: > > C:/COMMAND/MINGW32/BIN/MAKE.EXE > > (on my system) > > Needless to say, it is impossible to use the $(MAKE) variable for > executing the make program :( Why not? When I try using $(MAKE) in a makefile command like this: default: echo $(MAKE) $(MAKE) --version It works fine under both Windows 98 command.com and MSYS bash. The same also works under MSYS make, for which $(MAKE) is set to just "make". > > Using the full path would be OK, but why convert back slashes to > forward slashes? Is this Cygwin heritage or something? > > /Marcus It was probably done this way so that Mingw make could be used under the Cygwin shell, but normally it is best to use Cygwin make in this case. Is there a particular reason why you are using Mingw make instead of Cygwin/MSYS make? Are you using command.com or sh.exe to execute makefile commands? Luke Dunstan |