Re: [jamboost] Re: The right configuration mechanism

From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-08-12 05:14:12

On Friday 05 August 2005 23:00, David Abrahams wrote:

> > Wanting to always satisfy as many people as possible I would prefer
> > to have a way of handling all (a), (b), and (c). And it could be
> > done if we do (c) out of the box with a more intelligent default
> > user-config. Having (a) available as "using all : all ;" for all
> > toolsets and "using msvc : all ;" for individual ones. And having
> > (b) available as "using all : default ;" and "using msvc :
> > default;".
>
> That's the wrong syntax for this purpose. "using" just configures a
> toolset; it doesn't say what will be used to build with. I would say:
>
> default-toolset msvc-* gcc intel-8.1 ;
>
> Build with all versions of msvc, whatever the default (1st configured)
> gcc version is, and intel-8.1, unless the user puts a toolset name on
> the command-line.

I think the same can be achieved already by putting the following to 
user-config.jam:

project : default-build <toolset>msvc-6.0 <toolset>msvc-7.1 ;

All projects will be now built with two compilers. OTOH, I have no idea what
happens if some projects redefines 'default-build'.

> I'm slightly concerned about the special status we're according to
> C/C++ compiler suites here. What happens if there are several
> html->pdf conversion toolsets?

We can use 

configure all-c++-compilers : all ;

by creating file called "all-c++-compilers.jam" and implementing it's "init" 
rule accordingly. It might be bettet to use explicit "all-versions" as 
argument, though.

- Volodya

-- 
Vladimir Prus
http://vladimir_prus.blogspot.com
Boost.Build V2: http://boost.org/boost-build2