On 06.02.2018 18:08, Steven Watanabe via Boost-build wrote:

AMDG

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.

OK, I'll send a note / question to the Boost list to see who else is using the `python-tag` rule.

- --layout=system should probably continue using the current
  naming scheme (python/python3)

Hmm, more and more distributions rename 'python' to 'python2' to prepare for a pending move to Python 3 by default. So I'd like to propose we follow that trend.

- 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.).

I'm not sure I understand, but I'll look at the code to figure out what that "versioned-1.66" scheme is.

Thanks,

-- 

      ...ich hab' noch einen Koffer in Berlin...