Re: [Boost-docs] [quickbook] bjam failure.

Subject: Re: [Boost-docs] [quickbook] bjam failure.
From: Daniel James (daniel_at_[hidden])
Date: 2013-12-28 00:04:16

On 27 December 2013 23:25, Mostafa <mostafa_working_away_at_[hidden]> wrote:
> On Fri, 27 Dec 2013 07:19:54 -0800, Daniel James <daniel_at_[hidden]>
> wrote:
>
>> On 27 December 2013 05:17, Mostafa <mostafa_working_away_at_[hidden]> wrote:
>>>
>>>
>>> BTW, I'm only interested in building documentation, so I only cloned the
>>> submodules in the tools directory. Could this be part of the problem?
>>
>>
>> Yes, quickbook depends on several boost libraries. If you want to
>> avoid cloning all of boost, you can build quickbook from the last
>> boost release. Then to use it, you just need to tell boost build where
>> to find the executable, by adding to your 'user-config.jam':
>>
>> using quickbook : path/to/quickbook.exe ;
>
>
> Thanks, now I'm getting somewhere. So, I've built quickbook.exe from Boost
> 1.53 and the rest of the tools I'm using are directly from the head of the
> git repo. I'm able to generate html documentation from qbk files, but their
> slightly different from what's checked-in. Example, in libs/range/doc I ran
> ../../../tools/build/bjam.exe and get diffs along the following lines:
>
> -<div class="section range_reference_utilities_join">
> +<div class="section">
>
> 1) Is this because of my non-standard setup? Should I just clone everything?

No, that's because the range documentation was built with an different
version of boostbook. It's no problem.

> 2) How can I output html for just a single qbk file instead of the whole
> suite?

That's tricky I'm afraid. Firstly, you can only directly use quickbook
files that start with a docinfo block (for range, that's the 'library'
block at the beginning of boost_range.qbk). Secondly, converting
boostbook to html is tricky. The easiest way to do it is probably to
create a new quickbook file that just includes the file you want, and
add an entry to the jamfile (should be able to copy what's already
there). The quickbook file could be something like:

[article Range article
    [quickbook 1.5]
]

[include my_file.qbk]