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

Subject: Re: [Boost-build] Use of path-constant cygwin vs VSCommand Prompt
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2009-04-03 17:55:48

AMDG

Brian Davis wrote:
> 2) A desire to build msvc and gcc in one environment (second question).  The
> problem here is obviously cygwin paths mixing with windows paths.  It's 50%
> there as the actions use E:\whatever or C:\whateever, but the modules are
> using /cygdrive/e/... and /cygdrive/f.  What would be desired here is that
> when msvc is specified that the jam modules would use E:\whatever or
> C:\whatever not /cydrive/e etc.
>
> Now the second question is obviously a desirement, but I have configured
> Eclipse Project(right-click)->C/C++ Build and added a configuration for
> Win32 specifying .../jam/src/bjam.ntx86 for the PATH and set a Cygwin build
> configuration specifying .../jam/src/bjam.cygwinx86 in the PATH for that
> configuration and this allows me to somewhat quickly build and test msvc and
> gcc.  However bjam toolset=msvc,gcc -d+2 would be quicker in cygwin.
>   

I use a windows build of bjam under both windows and cygwin.
I run it from the cygwin shell to make sure that the environment
is set up correctly.  In user-config.jam in addition to initializing the
toolsets, I have
  toolset.add-requirements <toolset>gcc:<target-os>cygwin ;
with this setup
  bjam gcc msvc
works just fine.

In Christ,
Steven Watanabe