|
Boost-Build : |
From: Tim Slattery (Slattery_T_at_[hidden])
Date: 2006-12-19 09:12:21
"Andreas Fredriksson" <deplinenoise_at_[hidden]> wrote:
>On 12/18/06, Vladimir Prus <ghost_at_[hidden]> wrote:
>> Which shell is that that does not like forward slashes. I think all versions of Windows
>> I ever used had no problems with forward slashes. I don't say that you shell is "wrong",
>> but I'd like to know what's the actual problem here.
>
>The vanilla cmd shell in windows doesn't accept forward slashes. Or
>rather, the programs supplied with that shell don't:
>
>C:\temp>mkdir foo
>C:\temp>mkdir foo\bar
>C:\temp>dir foo/bar
>Parameter format not correct - "bar".
That's because the "dir" command, and most of the others too, use the
forward slash as an indicator that a flag follows. In *nix systems you
use the dash (-) for that. In Windows, it's either dash or forward
slash.
If you surround the path with doublequotes, it will work:
C:\temp>dir "foo/bar"
The doublequotes make the whole thing a single argument, and the
first argument is the path.
--
Tim Slattery
Slattery_T_at_[hidden]
http://members.cox.net/slatteryt
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk