Boost logo

Boost-Build :

From: Larry Evans (cppljevans_at_[hidden])
Date: 2005-10-08 08:28:04


On 10/08/2005 07:40 AM, Larry Evans wrote:
> On 10/06/2005 05:45 AM, Larry Evans wrote:
>
>>Does anyone know why:
>>
>> autodoc.boostbook cannot be loaded
>> boost/algorithm/string.hpp cannot be found
>>
>>as indicated in the following output?
>>
>><----------- output -----------------
>>cd /home/evansl/prog_dev/boost-release/1_33_0/libs/algorithm/string/doc/
>>bjam --v2 string_algo
>
> [snip]
>
> The problem doesn't occur with:
>
> cd /home/evansl/prog_dev/boost-release/1_33_0/doc
> bjam --v2 doc
>
> but I'd rather not update all the documentation when I'm only testing
> documentation for just my code. The closes I've come to just
> updating my documentation involves modifying the doc target:
>
> $(BOOST_ROOT)/doc/Jamfile.v2
>
> to just contain:
>
> boostbook doc : src/boost.xml
> :
> <dependency>../sandbox/lje/libs/fields_visitor/doc//reference.xml
> <xsl:param>boost.libraries=../../libs/libraries.htm
>
> ;
>
> and also modifying the <part> element of:
>
> $(BOOST_ROOT)/doc/src/boost.xml
>
>
> to just contain:
>
> <part id="libraries">
> <title>The Boost C++ Libraries</title>
>
> <xi:include href=
> "../../sandbox/lje/libs/fields_visitor/doc/users_guide.xml"
> />
>
> </part>
>
> Is there an easier way, i.e. one in which I just do:
>
> cd $(BOOST_ROOT)/sandbox/lje/libs/fields_visitor/doc
> bjam --v2 users_guide
>
> ?
Surprise. the following:

cd $BOOST_ROOT/sandbox/lje/libs/fields_visitor/doc/
bjam --v2 users_guide

now works, apparently because of this:

evansl_at_null:$ ls reference.boostbook
reference.boostbook

and reference.boostbook is there because of the earlier:

> cd /home/evansl/prog_dev/boost-release/1_33_0/doc
> bjam --v2 doc

What's so confusing is that for many libraries, e.g. SomeLibrary,
the Jamfile.v2:

$BOOST_ROOT/libs/SomeLibrary/doc/Jamfile.v2

contains:

boostbook SomeLibrary : SomeLibrary.xml ;

doxygen autodoc
...
:

where SomeLibrary.xml contains:

<xi:include href="autodoc.boostbook"/>

which requires the output from:

doxygen autodoc
...
:
be placed in the same directory as the SomeLibrary.xml; yet,
at least on my Debian linux, it's placed in:

$BOOST_ROOT/bin.v2/SomeLib/doc/gcc/debug/

Hasn't anyone else encountered this problem?

 


Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk