Subject: Re: [boost] [release] Boost 1.66.0 Beta 1 Release Candidate 1
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2017-12-09 03:40:55
On 12/08/2017 08:18 PM, Stefan Seefeld via Boost wrote:
> I see, thanks. What would be the "correct" fix for this, i.e. where
> would this `python-version` feature have to be defined (and used) to
> allow `b2` to be usable as intended, i.e. building for both, Python2 and
> Python3 in a single run ?
The right place is either build/src/tools/python.jam
or the Boost.Python Jamfile. Hmm. It looks like there's
already code to handle this (<python>). I wonder why
it doesn't work.
> (I take it even with this it would still not be possible to build
> against two arbitrary Python versions, as the feature as it is defined
> now will only distinguish between '2' and '3', rather than taking the
> exact Python version into account, as it does for toolchain versions.)
This is just a quick hack. The version could be
any string. The library names also need to be
mangled. If I remember correctly, the current
Jamfile only distinguishes boost_python and boost_python3.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk