Re: [boost] boost-install-ing zlib (Was: Re: [Release] Boost 1.70.0 Beta 1 Release Candidate 2)

Subject: Re: [boost] boost-install-ing zlib (Was: Re: [Release] Boost 1.70.0 Beta 1 Release Candidate 2)
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2019-03-13 18:45:20

AMDG

On 3/13/19 12:14 PM, Peter Dimov via Boost wrote:
>> I'll need to try and see what happens with <source> in user-config.
>> Probably nothing good, because one would expect neither <build-name>
>> nor <tag> to be specified in such a case.
> 
> If I remove the check for ZLIB_SOURCE, and just do
> 
> Â Â  alias boost_zlib : /zlib//zlib ;
> Â Â  libraries-to-install += boost_zlib ;
> 
> unconditionally in libs/iostreams/build/Jamfile, this is what happens:
> 
> - when `using zlib : : <source>C:/Projects/zlib-1.2.11 ;` is in
> user-config, the default `b2 install` fails because `address-model=32,64
> variant=debug,release` conflict as all try to build `libz.lib`.

This is a known issue and I have plans for fixing it.

Brief outline:

iostreams/build/Jamfile:

import zlib ;
# This will apply if a source directory is specified
# but no <tag> or <build-name>.  Explicit control of
# the library name in a config file will override it.
zlib.add-default-name boost_zlib : @boostcpp.tag ;
# use /zlib//boost_zlib instead of /zlib//zlib

> When
> address-model=32 variant=debug is given, `libz.lib` is installed in
> C:\Boost\lib, and the CMake configuration for boost_zlib correctly
> points to it.
> 
> - when using a prebuilt `using zlib : : <include>C:/Projects/include
> <search>C:/Projects/lib <name>zlib-8 ;`, the CMake configuration file
> for boost_zlib points to "${_BOOST_LIBDIR}/zlib-8", which is not correct.
> 

I think this should be handled by checking for SEARCHED_LIB
targets (in generate-cmake-variant maybe?)

In Christ,
Steven Watanabe