[boost] Re: Long toolset names

From: David Abrahams (dave_at_[hidden])
Date: 2004-10-03 18:39:16

Aleksey Gurtovoy <agurtovoy_at_[hidden]> writes:

> David Abrahams writes:
>> "Aleksey Gurtovoy" <agurtovoy_at_[hidden]> writes:
>>
>>> David Abrahams writes:
>>>> Aleksey Gurtovoy <agurtovoy_at_[hidden]> writes:
>>>> 
>>>> > What should we do about the following Boost.Build toolsets which
>>>> > filename's length exceeds 31 characters:
>>>> >
>>>> >     tools/build/v1/como-win32-4.3.3-vc7.1-tools.jam
>>>> >     tools/build/v1/intel-win32-7.1-vc6-stlport-4.5.3-tools.jam
>>>> >
>>>> > ?
>>>> 
>>>> Sorry to state the obvious, but... shorten the names?
>>>
>>> How exactly? Every part of the name carries essential information that 
>>> cannot be omitted without disabling other possible configurations. 
>>
>> Simple; we just change the build/test system to allow the abstract
>> toolset name to differ from the filename.  The file could contain the
>> actual toolset name if neccessary:
>>
>> icl-7.1-vc6-stlport-4.5.3-tools.jam:
>>
>>        toolset-name intel-win32-7.1-vc6-stlport-4.5.3 ;
>>        extends-toolset intel-win32 ;
>>        ...
>
> I like it. If we can have this sometime soon, it's going to save me
> some (minor) work on adjusting expected results/explicit failures
> markup to reflect the new names. If not, though, I'll go with what
> Rene and I have worked out.

I don't know enough about where the test system gets the names it
uses to make the modifications myself, if that's what you had in mind.

Sorry,

-- 
Dave Abrahams
Boost Consulting
http://www.boost-consulting.com