Re: [jamboost] Toolset tweaks: multi-element 'command'

From: Michael Stevens (Michael.Stevens_at_[hidden])
Date: 2004-06-29 03:45:19

Volodya,

On Tuesday 29 June 2004 08:23, Vladimir Prus wrote:
> I think I've done the final tweak to toolset's init: all of them now accept
> multi-element "command" parameter, so
>
> using gcc : distcc : distcc g++ ;
>
> should work. The elements are individually quoted on the command line, and
> the check for existance is done of the first element, so no bogus warning
> should be emitted.

Thanks for this. I have given it a bit of a stress test do I can give you some 
feedback.

There is a minor annoyance in the error reporting. Specifying a 
"user-provided-command" to "get-invocation-command" with
using gcc : distcc : XX g++ ;
gives the error
warning: toolset gcc initialization: can't find tool g++
warning: initialized from /home/michael/user-config.jam:21
which is rather confusing!

I am seeing an error when invoking "msvc" builds from
targets.jam:1157: in construct from module object(exe-target-class)@1

However since I have a very unusual cross compling (with Wine) build setup I 
cannot confirm if this is a normal problem or something my setup is 
introducing.

A few side issues that I am look
As ever the complexity of initialising MSVC looks with all the possible setup 
prefixes such as "vcvars32.bat" looks to be difficult. For my cross builds I 
simply need to bypass all the normal "setup" code and have my user specified 
command used directly. This command is in fact a shell script which does the 
Wine setup. I am looking at a way to incorporate this without effecting the 
existing logic.

As a minor point ".initialized" seems to be no longer necessary in "msvc.jam"

All the best,
Michael