Re: Patch: gcc -mno-cygwin support in Boost.Build v2.

From: Vincent N. Virgilio (virgilio_at_[hidden])
Date: 2004-03-31 04:35:01

Hi Volodya,

Is toolset gcc-nocygwin supported in Boost.Build v2? There is a thread 
about it for Boost.Build v1, which happened around 1 year ago. But I 
don't see any discussion about it centered on v2. Perhaps it has turned 
into a compile/link flag, per your earlier advice in this thread.

Vladimir Prus wrote:

> Hi Vincent,
> 
> 
>>I shouldn't be so terse. I meant TOOLS as in "bjam -sTOOLS=gcc". Is
>>there a way to specify a default for that bjam command-line option?
> 
> 
> Not exactly that, since V2 does not use -sTOOLS, but something close is 
> possible, in a number of ways:
> 
> 1. The toolset which is first defined in 'user-config.jam'/'site-config.jam' 
> becomes default.

When I insert statement "using gcc-nocygwin ;" in user-config.jam, bjam 
fails. It complains that it can't find gnu-nocygwin.jam

> 
> 2. You can change default toolset for your project with
> 
> project
> : default-build <toolset>msvc
> ;

This fails in a way similar to the above failure.

> 
> 3. You can also change default toolset globally by
> 
> import feature ;
> feature.set-default toolset : msvc ;
> 
> but this is probably not needed since you have (1)
> 

I'll use the compile/link flags for now.

> HTH,
> Volodya

Indeed. Thanks.

-- 
Vince