Boost logo

Boost :

Subject: Re: [boost] Boost.Log: Any Comments? (Was: [log] Permission to merge to trunk)
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2013-04-16 14:36:45


On Tuesday 16 April 2013 10:45:45 Daniel James wrote:
>
> No, I just run b2 in 'libs/logs/doc'.

I tried this in trunk and it doesn't work. The build log ends with this:

quickbook.quickbook-to-boostbook
../../../bin.v2/libs/log/doc/gcc-4.7/debug/log_doc.xml
Generating Output File: ../../../bin.v2/libs/log/doc/gcc-4.7/debug/log_doc.xml
...skipped <p../../../bin.v2/libs/log/doc/gcc-4.7/debug>log_doc.docbook for
lack of <p../../../bin.v2/libs/log/doc/gcc-4.7/debug-object(xinclude-
scanner)@2006>log_doc.xml...
...skipped <phtml>log_HTML.manifest for lack of
<p../../../bin.v2/libs/log/doc/gcc-4.7/debug>log_doc.docbook...
...skipped 2 targets...
...updated 52 targets...

The bin.v2/libs/log/doc/gcc-4.7/debug/log_doc.xml is present. I get similar
result if I try to build from Boost root, but the docs build fine in release
branch. What could be the problem?


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk