My current results are: ...patience... ...found 1311 targets... ...updating 7 targets... common.mkdir bin common.mkdir bin/gcc-4.4.3 common.mkdir bin/gcc-4.4.3/debug quickbook.quickbook-to-boostbook bin/gcc-4.4.3/debug/test.xml Generating Output File: bin/gcc-4.4.3/debug/test.xml xslt-xsltproc bin/gcc-4.4.3/debug/test.docbook xslt-xsltproc bin/gcc-4.4.3/debug/test.html warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl" compilation error: file /usr/local/share/boost-trunk/tools/boostbook/xsl/html-single.xsl line 15 element import xsl:import : unable to load http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/html/admon.xsl" compilation error: file /usr/local/share/boost-trunk/tools/boostbook/xsl/admon.xsl line 12 element import xsl:import : unable to load http://docbook.sourceforge.net/release/xsl/current/html/admon.xsl warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/lib/lib.xsl" compilation error: file /usr/local/share/boost-trunk/tools/boostbook/xsl/relative-href.xsl line 12 element import xsl:import : unable to load http://docbook.sourceforge.net/release/xsl/current/lib/lib.xsl XML_CATALOG_FILES="bin/boostbook_catalog.xml" export XML_CATALOG_FILES "/usr/bin/xsltproc" --stringparam chunk.first.sections "1" --stringparam chunk.section.depth "4" --stringparam generate.section.toc.level "4" --stringparam toc.max.depth "3" --stringparam toc.section.depth "3" --xinclude -o "bin/gcc-4.4.3/debug/test.html" "/usr/local/share/boost-trunk/tools/boostbook/xsl/html-single.xsl" "bin/gcc-4.4.3/debug/test.docbook" ...failed xslt-xsltproc bin/gcc-4.4.3/debug/test.html... ...failed updating 1 target... ...updated 6 targets... So this is still failing with the above simple qbk file, any thoughts? On Fri, Aug 13, 2010 at 2:00 AM, Daniel James <dnljms@gmail.com> wrote:
On Fri, Aug 13, 2010 at 12:58 AM, Daniel James <dnljms@gmail.com> wrote:
And running bjam complains about not having found boost, which makes sense since boost was build as a different user so its building directory is inaccessible.
If you use a prebuilt quickbook (you need to specify the location in your user-config.jam), you'll only need read access to the boost repository. If you set $BOOST_ROOT to its location, you should be okay. This is just to access boost build, the xsl stylesheets and dtd files.
Is there any way to remove the dependency on bjam?
Apparently, boost-cmake can (or perhaps could) build quickbook documentation:
http://article.gmane.org/gmane.comp.lib.boost.cmake/336
Other than that, it's complicated, there's a lot of parts to get right. You can see what bjam's doing by running 'bjam -n'.
Ooo, thanks for the hint, shall look at that. On Fri, Aug 13, 2010 at 2:58 AM, John Maddock <boost.regex@virgin.net> wrote:
Is there any way to remove the dependency on bjam?
It's somewhat Windows specific, but take a look at libs/math/doc/sf_and_dist/win32_nmake.mak which provides an example makefile for building without bjam.
HTH, John.
Hmm, I shall examine that too...