From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-11-15 12:10:38
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
On a related note, we need a way to that python-version is not added to target
paths of all targets, only to Boost.Python and python extensions.
> >> I'm not sure what you mean. bjam invokes cygwin gcc. Do you mean
> >> that bjam must be invoked under the cygwin shell? That's not true;
> >> you can build and test for cygwin gcc under an NT shell. I did that
> >> in part so I could test for cygwin and windows with a single bjam
> >> invocation.
> > So when running bjam in NT, you'll specify "/usr" for CYGWIN_PYTHON_ROOT
> > and that will eventually be passed to cygwin gcc -- which can understand
> > the "/usr" syntax. And NT bjam never does anything with "/usr" which
> > requires filesystem access?
> I don't know what you mean here.
> > I was confused by the fast that NT bjam can use cygwin paths.
> Or here.
> > So, when manually initializing python we need either to pass two paths:
> > using python : 2.3 : c:/python /usr/python ;
> > or allow to specify specific properties in initialization:
> > using python : 2.3 : c:/python ;
> > using python : 2.3 : c:/python : <toolset>gcc <toolset-flavour>cygwin
> > ;
> using python : 2.3 : /usr/python : <toolset>gcc
> <toolset-flavour>cygwin ;
> Something like that. I favor the latter. The former is too implicit.
Ok, I'll think how it can be implemented.
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