Hi,
I'm using boostbook to generate the reference documentation for the library I'm
working on. It
has improved a lot and now it is very good for the purpose I need.
But I have some questions/suggestions.
1. During the compilation I'm getting following messages and I don't know what they
mean:
xslt-xsltproc bin/gcc/debug/string_algo.doxygen.doxygen
xslt-xsltproc bin/gcc/debug/string_algo.doxygen.xml
-- Cannot handle sectiondef with kind=private-attrib
-- Cannot handle sectiondef with kind=private-type
-- Cannot handle sectiondef with kind=private-attrib
-- Cannot handle sectiondef with kind=private-static-attrib
xslt-xsltproc bin/gcc/debug/string_algo.doxygen.docbook
and
Writing id5216184-bb.html for refentry(id5216184-bb)
Writing id5216262-bb.html for refentry(id5216262-bb)
-- No template matches purpose in emphasis.
Writing struct.boost.string_algo.is_equal.html for
refentry(struct.boost.string_algo.is_equal)
-- No template matches purpose in emphasis.
Writing struct.boost.string_algo.is_iequal.html for
refentry(struct.boost.string_algo.is_iequal)
Writing struct.boost.string_algo.container_traits.html for
refentry(struct.boost.string_algo.container_traits)
Writing id5216859-bb.html for refentry(id5216859-bb)
2. Is there a way how to make lists in the reference? Doxygen can handle lists in
comments, but they
are not propagated to boostbook.
3. I have reported this issue before, but non has changed since then. So again.
To sucessfully execute boostbook build I have to manualy edit
$BOOST/tools/build/tools/doxygen.jam.
On the line 69 there is a hardcode link to some file.
local xsl-dir = [ boostbook.xsl-dir ] ;
DEPENDS $(target) : $(index-target) ;
xslt $(target) : $(index-target) "$(xsl-dir)/doxygen/collect.xsl"
---- :
<xsl:param>doxygen.xml.path=/home/gregod/Projects/Boost/boost/libs/any/doc/xml ;
Is this an error, or am I just missing something?
4. Link to files in the reference index are invalid. Links are always pointing to
$BOOST/boost/<header name>.hpp,
but my files are located in $BOOST/boost/string_algo/<header_name>.hpp so the link
is invalid.
5. Last point is just a wish. I have stated it before too, and I don't know what is
the status of it.
I would like to modify doxygen parameters during the build somehow. Currently the
build process only
generates the same doxygen file, and it is hard to do something with it.
I need to specify some additional flags to doxygen config. Namely macro
expasion is quite essential.
What I do now, it to let bjam generate default file, then I modify it an rerun th
doxygen manualy.
Next time bjam uses xml generated from my config.
I think it would be enough to add possibility to append a file to doxygen
config with custom settings.
Thanks.
Regards,
Pavol
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Boost-docs mailing list
[EMAIL PROTECTED]
Unsubscribe and other administrative requests:
https://lists.sourceforge.net/lists/listinfo/boost-docs
