Bob Friesenhahn wrote: > On Mon, 11 Jul 2005, Peter Ekberg wrote: > > You don't seem to understand what's going on... On MSYS there > > is no "official" way to convert a posix path to a win32 path > > (like cygpath on Cygwin). But if you execute any executable > > outside of the MSYS /bin or /usr/bin directories (and perhaps > > other places as well?), any argument that looks like a posix > > path is converted to a win32 path on the assumption that all > > such executables expect win32 paths. The problem is that in > > this case the conversion needs to be done not on an argument, > > but on an environment variable that MSYS does not autoconvert. > > So, it needs to be converted manually. So, since there is no > > official way to convert paths, I run a program outside of MSYS > > and as one of its arguments I have the posix path to be > > converted. The program I have chosen to run is the command > > This is the script I run under MSYS or Cygwin to convert a POSIX path > to a win32 paths with varying amount of escaping in case the result > needs to be handled by a script later. It has been pointed out to me > that Windows converts forward slashes to backslashes so it is not > necessary to generate backslashes, but paths are often seen > by Windows > users so I try to generate paths which are familiar to them.
[Script snipped] Yes, I came across that one, but it seemed heavy handed for the job at hand. I think my approach is neater, but I'm biased :-) In what way is your script better than my version that simply uses the cmd script from MSYS? Neither approach has a chance to work in a cross compile setup, which was the objection to my approach... Cheers, Peter
