Subject: Re: [Boost-build] Language specific include paths
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2018-02-19 18:39:54
On 02/19/2018 11:03 AM, Robert via Boost-build wrote:
> I would like to add that in order for zlib to successfully be part of
> the build, I have to use option "-s" on the b2 invocation:
> -s ZLIB_SOURCE="E:\ZLibSource\zlib-1.2.11" -s
ZLIB_SOURCE is enough. ZLIB_INCLUDE is actually
ignored if you pass ZLIB_SOURCE.
> Whether I can now build with zlib via user-config.jam, I have not tested
> it since roughly Boost 1.62.Â Keep in mind that I construct Boost for
> two different Windows compilers on Windows 8.1 Pro, x64 (e.g. Microsoft
> and Intel C++).
The problem is that the library name is not mangled, right?
This can be worked around by setting a <tag> rule that
does the mangling (with -s, it's added implicitly by
I just tried:
import boostcpp ;
using zlib : : <source>C:/path/to/zlib <tag>@boostcpp.tag ;
but that breaks because boostcpp.jam has bugs that
prevent it from being imported outside of Boost's
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