Daryle Walker wrote:
Is it possible to process Quickbook files, possibly in conjunction with
Doxygen-marked source files, without using bjam? If so, how?
Did you get it working with bjam? If so you could try running
bjam --v2 -a -n
And copy/paste the actual commands from the output. Here are some
commands filtered from building xpressive's docs output on linux, (each
actual command line starts with $.)
$ "doxygen"
../../../bin.v2/libs/xpressive/doc/gcc-4.0/debug/autodoc.doxyfile ;
<<< autodoc.doxyfile contains doxygen configuration parameters >>>
$ "xsltproc" --stringparam doxygen.xml.path
../../../libs/xpressive/doc/xml --xinclude -o
"../../../bin.v2/libs/xpressive/doc/gcc-4.0/debug/autodoc.doxygen"
"../../../tools/boostbook/xsl/doxygen/collect.xsl" "xml/index.xml"
<<< This and subsequent invocations of xsltproc may cause it to grab
DocBook stylesheets from the web. The build system creates a catalog
file that points to the local version of these files, if there is one.
The location of the file is passed in the environment variable
XML_CATALOG_FILES >>>
$ "xsltproc" --xinclude -o
"../../../bin.v2/libs/xpressive/doc/gcc-4.0/debug/autodoc.boostbook"
"../../../tools/boostbook/xsl/doxygen/doxygen2boostbook.xsl"
"../../../bin.v2/libs/xpressive/doc/gcc-4.0/debug/autodoc.doxygen"
$ cp
"../../../bin.v2/libs/xpressive/doc/gcc-4.0/debug/autodoc.boostbook"
"autodoc.boostbook"
<<< You can probably skip this step and adjust paths accordingly >>>
... Building QuickBook ...
<<< I'm assuming you'll also want to skip compilation of QuickBook and
dependencies... >>>
<<< If you're not using doxygen to extract documentation from code, this
is where you'd start. >>>
$ quickbook
--output-file=../../../bin.v2/libs/xpressive/doc/gcc-4.0/debug/xpressive.xml
xpressive.qbk
... This is where the Build system creates the catalog file ...
$ "xsltproc" --stringparam chunk.section.depth 3 --stringparam
toc.max.depth 3 --stringparam toc.section.depth 3 --xinclude -o
"../../../bin.v2/libs/xpressive/doc/gcc-4.0/debug/xpressive.docbook"
"../../../tools/boostbook/xsl/docbook.xsl"
"../../../bin.v2/libs/xpressive/doc/gcc-4.0/debug/xpressive.xml"
<<< You may want to adjust the stringparam options above or add/remove
to your taste >>
$ "xsltproc" --stringparam chunk.section.depth 3 --stringparam
toc.max.depth 3 --stringparam toc.section.depth 3 --xinclude -o "html/"
"../../../tools/boostbook/xsl/html.xsl"
"../../../bin.v2/libs/xpressive/doc/gcc-4.0/debug/xpressive.docbook"
Hope this possibly unreadable post helps,
-- João
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Boost-docs mailing list
[email protected]
Unsubscribe and other administrative requests:
https://lists.sourceforge.net/lists/listinfo/boost-docs