Re: [Boost-build] [doc] b2 headers

Subject: Re: [Boost-build] [doc] b2 headers
From: Mateusz Loskot (mateusz_at_[hidden])
Date: 2018-04-09 16:49:12

On 9 April 2018 at 16:09, Rene Rivera <grafikrobot_at_[hidden]> wrote:
> On Mon, Apr 9, 2018 at 8:35 AM, Mateusz Loskot via Boost-build
> <boost-build_at_[hidden]> wrote:
>>
>> TL;TR: A rant
>>
>>
>> I've been looking for documentation about purpose of command
>>
>> b2 headers
>>
>> Greping for headers or modular inside  /tools/build/doc and
>> /doc gives me nothing, so I blindly assume the unsearchable
>> https://www.boost.org/build/ does not explain it either.
>
>
> You could search here instead <https://grafikrobot.github.io/b2doc/>.

By the way, plug [1], can it have a search box?

[1] https://lists.boost.org/boost-build/2018/03/29878.php

>> The magic of https://www.google.com/search?q="b2+headers"
>> brought this page to my attention:
>> https://www.boost.org/doc/libs/master/tools/boostdep/doc/html/
>> where, to my surprise, I find one of best intro to the concept
>> of modular Boost including very helpful explanation of the virtual
>> /boost directory and role of b2 headers command.
>>
>> Why this kind of information is presented in docs for somewhat
>> exotic to Boost (end)users command, I have no idea.
>> But, as long-time Boost.Build users, I dare to judge this is an
>> excellent example of why people hate this awesome build system :)
>
>
> "b2 headers" is an entirely Boost C++ Libraries specific construct and other
> than using b2 has nothing to do with b2 itself.

Fair.

The b2doc makes sense

"
target
    All tokens that are neither options nor properties specify what
targets to build.
"

Does it mean, it is guaranteed that single word in b2 command line
always means a target name?

And, as a target name, it is a thing specific to particular build configuration.

> The same applies to all the rest of that documentation you just pointed out :-)
> And hence why it's not in the b2 documentation.
> Hence what you are actually saying is that people
> hate the Boost C++ Libraries setup and not b2. And I don't blame them.. I
> don't like it either ;-) Which is why I've been working to put as much
> distance between Boost C++ Libraries and b2.

I'm greatful for your efforts!

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net