Subject: Re: [Boost-build] Language specific include paths
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2018-02-14 17:04:31
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.
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