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

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-06-23 08:47:18

Michael Stevens wrote:

> > 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.

Yea, and it would allow me to write very nice docs on "using" ;-) That's what 
has prompted me to do this cleanup now.

> 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. 

Oops! I've changed gcc to use get-invocation-command an hour ago.

> 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.

Yes, I think this might be the right solution. We also have to figure out what 
to do with the shell -- I've just tried the "distcc g++" command and shell 
barks, just like Jürgen has said.

(Not 100% ontopic, but: we have distcc here by creating a number of wrapper 
scripts in /usr/local/bin/distcc, which just call "distcc /usr/bin/g++". In 
means that to switch distcc on it's only necessary to change PATH. This might 
not be a good solution for you......
)

> 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.

Yea.

> 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 !

Well, we can state in docs that some toolset interpret "version" specially, 
though it's a bit backward, after making sure that all toolset interpret 
"command" in the same way ;-)

I'm puzzled.

- Volodya