Re: [Boost-testing] Toolset Autoconfiguration [was: Martin Wille x86_64 V2 - python]

From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2007-03-26 16:03:22

David Abrahams wrote:
> Let me give you a few examples of questions that have not been answered:
> 
> 1. Is it possible that the version or the toolset name contains a dash
>    (it always used to be possible to make a toolset name containing a
>    dash, c.f. intel-win)

NAFAIK. I've tried using "-" as part of the version number, for example, 
and failed. I've ended up using "~" instead when I need to have some 
special kind of version.

> 2. If one substring is numeric, does that necessarily constitute the
>    version number?

No.

> 3. When invoking the toolset's "init" rule to configure it, what
>    should I do with any additional dash-separated substrings?  

Since there is all IMHO...

1. I'd say change the toolsets to accept a list of values for the 
version (all of the are "version ?" args now).

2. And have that version passed directly to the 
"common.check-init-parameters" rule.

3. Change the check-init-parameters to:

     rule check-init-parameters ( toolset version * : * )

And to interpret the version values as (version,flavor). Hence the 
enforced format would be "/toolset/-/version/-/flavor/".

Basically, we aren't going to get anywhere unless we just decide on 
something. So the above is my decision :-)

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo