Re: Generating HTML from BoostBook XML (was Re: [boost] Should I use std::get or boost::get (or both) in Boost.Array)

Marshall Clow <[email protected]>
Newsgroups gmane.comp.lib.boost.documentation
Message-ID <[email protected]>
On Dec 19, 2012, at 11:41 AM, Daniel James <[email protected]> wrote:

> On 19 December 2012 19:32, Marshall Clow <[email protected]> wrote:
>> [ Resending to the -docs list ]
>> 
>> I'm updating the Boost.Array documentation to describe the changes I made, and the only source file there is BoostBook XML.
>> That's unfortunate, but OK, I can edit that.
>> 
>> But how do I turn it into HTML?
>> There's no Jamfile in the libs/array/doc directory, just a XML file.
>> 
>> [ Note: I believe I have all the pieces installed correctly; I can generate documentation for other libraries. ]
> 
> It's normally just built as part of the combined documentation, which
> wasn't so horrendously slow when the array documentation was
> originally written. You can add a Jamfile if you want to build
> standalone documentation. Something like:
> 
> using boostbook ;
> boostbook standalone : array.xml : <xsl:param>boost.root=../../../.. ;

I'm adding the docs for string_ref to Boost.Utility. (Ok, I added them a while back, but never got them building correctly).

Boost.Utility's docs are a mixture of hand-written HTML and Quickbook - declval, for example is generated by QB.

I duplicated the declval.qbk file, edited it, and then updated the Jamfile.
Unfortunately, when I run b2, I get an XML file in the bin.v2 directory, not an HTML file in the doc/html directory.

I'd appreciate it if someone could take a look at the Boost.Utility docs and let me know what I'm doing wrong.

Thanks in advance!

-- Marshall

Marshall Clow     Idio Software   <mailto:[email protected]>

A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait).
        -- Yu Suzuki
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.