Re: [Boost-build] CVS: boost/tools/build/v2/tools gcc.jam, 1.68, 1.69 msvc.jam, 1.76, 1.77 rc.jam, 1.8, 1.9

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-04-07 03:18:32

Rene Rivera wrote:

>>> +
>>> +    #~ - The resource compiler.
>>> +    local rc =
>>> +        [ common.get-invocation-command gcc
>>> +            : windres : [ feature.get-values <rc> : $(options) ] :
>>> $(bin)
>>> : PATH ] ; +    local rc-type =
>>> +        [ feature.get-values <rc-type> : $(options) ] ;
>>> +    rc-type ?= windres ;
>>> +    rc.configure $(rc) : $(condition) : <rc-type>$(rc-type) ;
>> 
>> Rene, with this patch you'll get:
>> 
>>    warning: toolset gcc initialization: can't find tool windres
>> 
>> on a vanilla Linux system, becase 'common.get-invocation-command' checks
>> if the tool exists. Maybe, this logic should be activated only on
>> NT/CYGWIN?
> 
> What about cross-compilation, which is what I'm trying to eventually
> support? 

I suppose even in that case there should be some checking. If you're going
to invoke windres under wine, then it should be possible to verify that

   wine ~/windows/....../windres

is the valid command.

> It might be better to pass an "optional" flag to 
> get-invocation-command?

Then, when 'windres' is not found, user won't see any warning. It might be
possible to issue the warning only when --debug-configuration is specified.
The reasoning would be that lack of 'windres' is less fatal cirsumstance
then lack of 'gcc'.

I'd be happy with any option, in fact, as soon as we don't get warning on
Linux.

- Volodya