On 2/1/06 6:50 PM, "João Abecasis" <[EMAIL PROTECTED]> wrote:
> 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 No, because I haven't gotten bjam to work. I don't want to bother if I can use Quickbook without bjam. I especially want to process files that are not within the Boost file hierarchy (since they're trial libraries). > > 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 ; I don't have an "autodoc.doxyfile" file on my system at all. Where does it come from? (And can there be one that isn't compiler-specific?) > > <<< 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... >>> Well, if QuickBook is a separate executable, then I'll need to compile it too (without bjam if possible). > > <<< 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, I wonder if we could make a shell script that takes in a list of *.qbk files and/or any C++ source/header files and processes them through Doxygen, QuickBook, and xsltproc to a specified output directory. (Then bjam could call that script.) -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com ------------------------------------------------------- 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&kid3432&bid#0486&dat1642 _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
