Re: [jamboost] Re: Toolset init changes: gcc, intel and sun

From: Michael Stevens (Michael.Stevens_at_[hidden])
Date: 2004-06-23 08:22:00

On Wednesday 23 June 2004 09:45, Vladimir Prus wrote:

> Christopher Currie wrote:
> > Vladimir Prus wrote:
> > > I've just made another round of simplifying toolset initialization, and
> > > touched gcc, intel and sun. The changes are:
> >
> > This is a welcome change and improvement, thanks for making it so clean!
> > This now allows me a configuration I've always wanted, which is the
> > ability to support the Purify tool as a version of the compiler:
> >
> > using sun : purify : "purify CC" ;
> >
> > allows me to use "bjam sun-purify" as an alternate toolset. Great work!
>
> Cool. I wonder, though, if the above "using" syntax gives you a warning
> that compiler is not found? Of course, that's only a warning, but would be
> nice to kill it.

Volodya thanks for all the work on this. The new toolset command line 
structure is much better.

Like Christopher I particularly like the change so I can run compilers with 
prefixes. "distcc" for example.
So I am glad the gcc toolset does not need to call "get-invocation-command" 
and warn. One possibility in this regard would be to allow 
"user-provided-command" to contain two elements. The first element could be 
the prefix, and the second the actual command. Only the latter would be use 
to fine the tool path.

This would provide a general prefixing solution without having to add 
additional init parameters.

I have also been thinking about the meaning of the init 'version' parameters.
This particularly interest me as I do things like
using intel : 8.0 ;
using intel : myspecialtest : "special compiler" : "special options";

For this purpose 'version' is simply a user defined freeform tag. It can be 
used to specify build targets and matched in optional properties for specific 
build requirements.

The exception to this freeform rule is the 'msvc' toolset. Here the 'version' 
parameter has meaning and is used to automagically choose paths and options.
I not sure of a good solution to this dichotomy !

Michael