Integrate building of html docs into boost's doc build

[Nathan Ridge]

Boost.Range uses Quickbook for its documentation. The generated HTML files are currently checked into the repository.

According to Eric Niebler (​http://permalink.gmane.org/gmane.comp.lib.boost.devel/236447):

"[I]t's generally discouraged to check in generated files. This goes for html that's generated from quickbook. The preferred thing for docs is to integrate your library's doc build with the overall boost doc build by editing $BOOST/doc/Jamfile.v2."

We should do this for the Boost.Range docs.

[Michel Morin]

ATM, let's delete libs/range/doc/html/quickbook_HTML.manifest. This file is completely unnecessary for the end users.

[Nathan Ridge]

Replying to michel:

ATM, let's delete libs/range/doc/html/quickbook_HTML.manifest. This file is completely unnecessary for the end users.

Unnecessary, yes, but does it hurt to leave it there? I find this file useful because the diff to it tells me which HTML files to "svn add" or "svn remove" after re-generating docs.

[Michel Morin]

Unnecessary, yes, but does it hurt to leave it there?

No, it doesn't hurt any thing; if that file is useful, it is not necessary to svn-delete it.

I pointed this out just because Boost.Range is the only library that commits quickbook_HTML.manifest.

[Nathan Ridge]

Replying to michel:

Unnecessary, yes, but does it hurt to leave it there?

No, it doesn't hurt any thing; if that file is useful, it is not necessary to svn-delete it.

I pointed this out just because Boost.Range is the only library that commits quickbook_HTML.manifest.

OK. I will leave it in for now, then when the doc build is integrated into the boost doc build, it will be gone along with whole html folder.

[Neil Groves]

The work was actually done by Daniel, but this is completed :-)