From: JonY <jo...@us...> - 2011-07-12 17:51:41
|
On 7/13/2011 01:26, George Brink wrote: > > On 7/12/2011 12:47 PM, JonY wrote: >> On 7/12/2011 23:57, George Brink wrote: >>> Using /c/ as a designation for the real root helped, thank you. >>> >>> But I do not understand what is the point of using MSYS as a shell? >>> The fact that MinGW can work from windows' native cmd.exe (and as a >>> result from ANY windows application) was the whole reason for me to >>> switch from cygwin to mingw. >>> >> >> Sure, if you can figure out how to run unix shell script with just cmd >> without msys/cygwin installed. > I do not see any real problem in that. Shell scripts are just programs, > they work primarily with external executable files but they are still > programs. After all, if we can use perl/awk/python/etc interpreters in > Windows without any shell substitution, why can't we use sh? > I'd like to be able to run `sh somescript.sh` from the standard Windows' > cmd.exe or any other Win-application which can run external applications. > Uh sure, you would already have MSYS/Cygwin installed at that point, so why not just use the tools that you have? You'll still have to deal with path translation anyway since you are already involved with using MSYS tools. >> Have you tried using msys "make" instead of "mingw32-make"? > Yes, but I do not see any real difference. msys-make is in fact gmake > 3.81, mingw-make is gmake 3.82. And that's it. > Both are behaving the same if you write a rule with an absolute path in it. > No, the former understands unix paths, the latter is good for makefiles with win32 type backslash paths, which you aren't using since you are calling a configure unix shell script. |