I've fiddled with the pathnames for a while with no success. I guess I'll have to delve deeper into how the whole thing is supposed to work. In the mean time, my original question remains unanswered. "Its not altogether clear from reading the documentation whether things like DOCBOOK_XSL_DIR should be an exported environmental variable with the value set to the appropriate directory or if the actual directory name should be substitued where DOCBOOK_XSL_DIR appears in the example." I've tried it both ways an no luck. The typefaces and code snippet in the manual seem to suggest the former - but a literal reading of the text suggests the latter. Robert Ramey John Maddock wrote:
Robert Ramey wrote:
OK - I didn't expect anything to require a C++ compiler just to build documentation I added using msvc : 7.1 and ran bjam --v2 - as per instructions on http://www.boost.org/doc/html/boostbook/setup/running.html
and things did crank way for quite a while and produced a lot of output on the console. It ended with an encouraging messsage (which I have since scrolled off the top of the screen). I run bjam --v2 again and it "finishes" pretty quickly with output which looks like:
...patience... ...found 1100 targets... ...updating 1 target... xslt-xsltproc-dir html\HTML.manifest warning: failed to load external entity "http://docbook.sourceforge.net/releas xsl/current/html/chunk.xsl"
That's the key message, it means one or both of the paths in the
using boostbook path1, path2 ;
declaration is wrong, double check your paths and hopefully you'll spot the error.
John.