On Thu, Aug 25, 2005 at 04:00:53PM -0400, DJ Delorie wrote: >> So, should it default to finding an executable on the path first and >> then look for MinGW/MSYS versions of the program if it can't find >> the executable on the path? > >Hmmm... 99% of the cases will be "#!/bin/sh" anyway. What's the >"right" shell to run for that in MinGW? If you can detect MinGW[*], >and check the right MinGW places first, that's probably the best >solution. > >[*] I'm thinking of an #ifdef in libiberty, nothing fancy.
The problem is that there's MinGW and there's MSYS. MSYS is a Cygwin fork that many MinGW people use as a build environment. I can detect that the compiler is a MinGW compiler but I can't necessarily detect, at compile time, that MSYS is being used. I can detect this at runtime, though, but that means building in MSYS awareness iff pex-win32.o is being built for MinGW. I guess that can't really hurt. cgf
