Subject: Re: [Boost-build] selecting Python version for Boost.Python
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2018-02-06 23:08:20
On 02/06/2018 03:40 PM, Stefan Seefeld via Boost-build wrote:
> So now that the library name has changed, I suppose there is at least
> one other change I need to add: Windows auto-linking support requires
> the library name to be encoded in some source (header) file, doesn't it ?
Right. It's in a header somewhere... probably named
config.hpp or autolink.hpp
> Any other changes I need to make, either to code or build logic, somewhere ?
- python-tag is used by libraries that depend on python (I think
mpi has python bindings). Make sure that the library naming
makes sense for those as well.
- --layout=system should probably continue using the current
naming scheme (python/python3)
- boostcpp.jam in develop has code to use an old naming scheme.
--layout=versioned-1.66 should use the old names. (This
is only intended to make updating Boost less painful
whenever we change library naming.).
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