Re: [Boost-users] [boost] Boost 1.61.0 Beta 1 Release Candidate 1

Subject: Re: [Boost-users] [boost] Boost 1.61.0 Beta 1 Release Candidate 1
From: Daniel James (dnljms_at_[hidden])
Date: 2016-03-21 17:48:17

On 20 March 2016 at 14:17, Rene Rivera <grafikrobot_at_[hidden]> wrote:
> On Sun, Mar 20, 2016 at 5:42 AM, Daniel James <dnljms_at_[hidden]> wrote:
>>
>> ASIO documentation is being built in the wrong place, which breaks a
>> few links. I build it using something like 'cd doc && b2 -q asio'.
>
>
> OK. I'll have to figure out why it's built in the wrong place when built
> indirectly from the root/doc dir.

I'm not sure which directory you mean as the wrong place. It's
supposed to be built under 'doc/html', which might be seen as wrong,
but moving it would break links.

> 1. I really, really, really, don't want to maintain manual lists of this
> stuff any longer. It's horribly error prone..

Guessing based on directory structure isn't much better. Btw. you also
need to check for 'libs/*/*/doc/', in order to generate documentation
for numeric/odeint, spirit/repository, functional/factory and
functional/forward. All of these have a 'sublibs' file, so maybe only
when that exists.

> 2. That list already misses some standalone docs. For example predef :-(

You're checking the built documentation in, so I don't overwrite it.

> 3. Since library authors don't know that manual list existed new libraries
> where not included.

I check every new library before it's released. so new libraries
aren't a problem. At least if the list is in the Jamfile people will
be more likely to find it than if it's in separate build file. I've
never been particularly happy that I had to maintain a separate layer
around the build system.