Re: [Mingw-users] (no subject)

[Earnie <ea...@us...>]

LRN wrote:
>  On 25.03.2010 18:51, Tristan Evain wrote:
> > Hi,
> >
> > I'm a new user of Msys, trying to execute a Win32 program via sh
> > command line. I need to pass arguments, including a windows style
> > path. Unfortunately, the utility I want to run doesn't accept
> > slashes for separator, and I cannot find how to avoid backslashes
> > substitution.
> >
> > My command is : $ runasspc /program:"c:\some_dir\some_program.exe"
> >
> > And runasspc get "c:/some_dir/some_program.exe" (i.e. with slashes)
> > , and fails running the program. I tried two, three and four
> > backslashes, with no effect.
> >
> > Is there a setting or an environment variable to set to deactivate
> > this feature ?
> >

You could try c:\\..\\somepath\\some.exe

>  I don't think so. MSys path mangling can't be disabled, as far as i
>  know. Causes some grief to me now and then. For example, you can't
>  call MS lib.exe (and most other MS utils which accept parameters as
>  "/foo:bar") from MSys. Also, you can't pass paths that end with ':'.

MS utilities parameters can be passed with //foo:bar.  What path ends in 
a colon, it isn't an allowed file system name.

>  For example, if you call configure script for GStreamer this way:
>  configure --with-pkg-config-path:/local/lib/pkgconfig: (note the
>  trailing ':') pkg-config won't find anything, because MSys wouldn't
>  know to convert "/local/lib/pkgconfig:" into
>  "c:\msys\1.0.11\local\lib\pkgconfig;"
>

Is this trailing colon a desirable thing?  What is the purpose here?

>  If it is disableable indeed, i would like to know that trick too.
>

Seems you don't know all the tricks. ;p

-- 
Earnie
-- http://www.for-my-kids.com