Re: The right configuration mechanism

From: Alexey Pakhunov (alexeypa_at_[hidden])
Date: 2005-08-14 11:18:38

Vladimir Prus wrote:

> So, 
> 
> configure gcc : : /usr/bin/g++-4.0 ;
> 
> will no longer work and you'll be required to write:
> 
> configure gcc : : command=/usr/bin/g++-4.0 ;
> 
> ?

Mmm... Yes. I thought we speak about introducing 'configure' and a new 
syntax for it.

> Ehm... what's the use of just detecting configuration, if it can only be used 
> after "using"? I.e. will detected configuration be stored in some cache 
> that's consulted by "using". Is this such performance optimization?

It is a kind of dilemma. In the one hand a user may want everything to 
be configured automatically (i.e. all detected version will be 
configured). In the other hand some users want to select the 
configuration they want to use or define own. It can be solved in the 
following way:

# all detected configuration
using msvc : all ;

# default autodetected configuration
using msvc : default ;

# 8.0 if it was detected or cl.exe is in PATH
using msvc : 8.0 ;

# overwrite 7.1 configuration
using msvc : 7.1 : command=<some custom path> ;
# use all other detected version
using msvc : all ;

Best regards/Venlig hislen,
Alexey Pakhunov.