Subject: Re: [Boost-build] Language specific include paths
From: Robert (r.firl_at_[hidden])
Date: 2018-02-19 18:03:53
On 2/14/2018 11:04 AM, Steven Watanabe via Boost-build wrote:
> On 02/14/2018 09:39 AM, Daniel James via Boost-build wrote:
>> On 14 February 2018 at 16:18, Steven Watanabe via Boost-build
>> <boost-build_at_[hidden]> wrote:
>>>> This is entirely due to
>>>> boost build's design.
>>> It's only the quickbook toolset that's a problem.
>>> Abusing include is just plain wrong.
>> The quickbook toolset is part of boost build, not quickbook. It also
>> looks like asciidoctor, sass
> asciidoctor and sass were both recently added
> and appear to be copying quickbook's brokenness
> here. (include doesn't even work in asciidoctor,
> because -I means something different.) I will
> fix these right now regardless of breakage.
>> and rc do the same thing,
> It's the right thing for rc, as rc is expected
> to find C/C++ headers.
>> maybe more. I'm
>> not sure, but the zlib and libjpeg toolsets might pick up include
>> paths that they're not meant to.
> I don't think so. The include paths from depending on
> /zlib//zlib will be added to whatever other include paths
> the target has, but that's unavoidable.
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
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++).
> In Christ,
> Steven Watanabe
> Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build
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