From: David Abrahams (dave_at_[hidden])
Date: 2004-11-18 16:13:57
Vladimir Prus <ghost_at_[hidden]> writes:
> On Tuesday 16 November 2004 19:42, David Abrahams wrote:
>> Vladimir Prus <ghost_at_[hidden]> writes:
>> >> > In case of Python, there's no property to make "2.2" subproperty
>> >> > of. There's no <toolset>python.
>> >> But why not?
>> > Because a property set can have only one value of <toolset>, at least
>> > it's now it works now. We can't have both <toolset>gcc and
>> > <toolset>python.
>> >> You are (ab)using toolsets for similar things like QT, IIRC.
>> > QT is a module in tools directory, true. But it's used by specifying
>> > <library>/qt//qt
>> > in requirements, not by another value of <toolset>
>> I suggest that Python introduces a feature called "python" with one
>> value: "python". Then it can have a version subfeature.
> Ok, this is certainly possible. Another approach is to make versions the
> values of the "python" feature, so you'd write
> bjam python=2.2 python=2.3
That works too, but might be a little confusing for users. At that
point I'd go with python-version=2.2
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk