From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-11-16 10:09:19
On Monday 15 November 2004 23:06, David Abrahams wrote:
> Vladimir Prus <ghost_at_[hidden]> writes:
> > On Sunday 14 November 2004 02:28, David Abrahams wrote:
> >> >> It's needed for people like me who want to be able to test against
> >> >> multiple Python versions.
> >> >
> >> > Ok. Is "python-version" property OK with you? So that it's possible to
> >> > write:
> >> >
> >> > bjam python-version=2.2 python-version=2.3
> >> >
> >> > ?
> >> Well, shouldn't this be a sub-property so you can write
> >> bjam python-2.2 python-2.3
> >> just like you can write
> >> bjam vc-7.1 vc-6.5
> >> ??
> > 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
in requirements, not by another value of <toolset>
> > On a related note, we need a way to that python-version is not added
> ^--- "say?"
> > to target paths of all targets, only to Boost.Python and python
> > extensions.
> I have no brilliant ideas for that.
Ok, I'll figure out something.
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