Re: [Boost-build] Change in behavior of lib task in 1.66.0

Subject: Re: [Boost-build] Change in behavior of lib task in 1.66.0
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2018-01-06 02:26:48

AMDG

On 01/05/2018 09:46 AM, Ian Emmons via Boost-build wrote:
> I am using Boost.Build as the build infrastructure for my own project. 
> I have the following setup:
> 
> * I use --layout=versioned when I build the Boost libraries.
> 
> * In site-config.jam, I have defined aliases for the precompiled Boost
> libraries that I use, like so:
> 
> alias BoostFileSystem
> Â  : # no sources
> Â  :
> <address-model>64,<link>shared,<variant>debug:<source>$(BoostDir)/stage/lib/libboost_filesystem-gcc48-mt-d-x64-1_66.so.1.66.0
> 
> <snip>I am guessing that
> starting in 1.66.0, Boost.Build no longer recognizes file names ending
> in a version as shared libraries, so it doesn't know what to do with them.
> 

Here's the cause of the problem:

$ cat Jamroot
import type ;
ECHO [ type.type libboost_filesystem.so.1.66.0 ] ;
$ b2
MANPAGE

If you remove src/tools/types/man.jam it should work again.

In Christ,
Steven Watanabe