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-20 08:42:01

On 20 March 2016 at 00:16, Daniel James <dnljms_at_[hidden]> wrote:
>
> I've put the documentation on the website. It's linked from the release notes:
>
> http://www.boost.org/users/history/version_1_61_0.html

I've compared the documentation build with my last build and found a
few issues (including one in my build). I don't think any are
important enough to delay the beta.

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'.

Libraries which are in the combined documentation are being built
twice, once for the combined documentation and once as standalone, for
example:

http://www.boost.org/doc/libs/1_61_0_b1/doc/html/xpressive.html
http://www.boost.org/doc/libs/1_61_0_b1/libs/xpressive/doc/html/

I've just manually maintained a list of documentation that need a
standalone build. The list is currently:

    geometry phoenix fusion spirit spirit/repository algorithm
    context coroutine coroutine2 numeric/odeint log tti
    functional/factory functional/forward range utility core
    convert test sort bind tuple python vmd compute hana

I guess the code added in doc/Jamfile.v2 could use that, instead of
globbing for all '*/doc' directories.

Some intermediate files are included. The way we've been doing it is
to build the documentation, then add the contents of the various
'html' directories to a zipfile, and extract that into a clean
checkout, so I've never kept a list of the unneeded files. Some
examples are:

doc/AutoDoxywarnings.log
doc/accumulators.tag
doc/dvips.version
doc/gs.version
libs/geometry/doc/doxy/ (everything in the directory).