Re: [Boost-build] Use of path-constant cygwin vs VSCommand Prompt

Subject: Re: [Boost-build] Use of path-constant cygwin vs VSCommand Prompt
From: Vladimir Prus (ghost_at_[hidden])
Date: 2009-04-03 01:15:22

On Friday 03 April 2009 04:43:26 Brian Davis wrote:
> I have the following Jamroot file below and I have been noticing a
> difference between MSVC command prompt and Cygwin (gcc).

Well, it's not MSVC command prompt, and gcc command prompt. Rather, it's
difference between running in Windows operating system, and the Cygwin
operating system. They happen to use different path naming conventions.
It is in general unclear if passing paths in Windows syntax to random
Cygwin problem is going to work, or not.

> I have two questions with this post:
> 
> 1) What is the dealy-o with path-constant where locals are involved in the
> path and what is the difference (besides the obvious syntax difference
> between ms and cygwin path/directory syntax)?
> 
> 2) Why does bjam swap between use of cygwin paths and dos paths in the build
> when in the cygwin environment building for toolset msvc

Can you clarify what problems does this cause?

- Volodya