From: Dave B. <bro...@ya...> - 2002-08-29 03:17:09
|
--- Infidel - <cod...@ho...> wrote: > > > > >From: Dave Brondsema <bro...@ya...> > >To: Luke Dunstan <cod...@ho...>, > >min...@li... > >Subject: Re: [Mingw-msys] posix and windows paths > >Date: Wed, 28 Aug 2002 19:46:31 -0700 (PDT) > > > >--- Luke Dunstan <cod...@ho...> wrote: > > > > > > ----- Original Message ----- > > > From: "Dave Brondsema" <bro...@ya...> > > > To: <min...@li...> > > > Sent: Thursday, August 29, 2002 10:10 AM > > > Subject: [Mingw-msys] posix and windows paths > > > > > > > > > > > > Backslashes have a special meaning to the bash shell. The > > > correct way in > > > MSYS is: > > > > > > cat /d/msys/1.0/t/test.sh > > > > > > Or: > > > > > > cat d:/msys/1.0/t/test.sh > > > > > > >Will this type of path work for all situations? It seems > that > >it's the only possibility for me. /d/msys/1.0/t/test.sh > won't > >work in the final executable outside of msys and > >d:\\msys\\1.0\\t\\test.sh requires changing \ to \\ under > >several conditions. > > > >The only possibility that comes to mind is `pwd`. It returns > a > >/d/msys/ style path unless the -W parameter is passed. BTW, > is > >this -W parameter available in msys only? > > Its hard to say unless you explain exactly what you are trying > to do. Are > you hard-coding a path in the source code for opening a file? > Are you using > system() or something similar to execute commands from your > program? Or are > you just trying to pass an argument to your program from the > MSYS command > line? > All of the above. I'm trying to port Qt 3.0.1 to run as a native windows library. This means paths in shell scripts, as parameters to executables, in code in qdir.cpp and qfile.cpp (which is used in qmake outside of msys when completed AND used by qmake to complete the compilation while still in msys). Dave Brondsema __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com |