Problems trying to use boost book
I'm interested in setting up quickbook/boostbook/docbook for my windows NT machine. To that end I've religously followed the instructions in http://www.boost.org/regression-logs/cs-win32_metacomm/doc/html/boostbook/ge... (Not including installing Java) I get to "Running Boost Book". Following the instructions there I invoke bjam --v2 and get: the following response $ bjam --v2 warning: Python location is not configured warning: the Boost.Python library won't be built Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). warning: no toolsets are configured. warning: you won't be able to build C++ programs. warning: please consult the documentation at warning: http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html I've verified the current directory $ pwd C:/BoostHead/doc and that xsltproc is in my path $ xsltproc Usage: xsltproc [options] stylesheet file [file ...] Options: --version or -V: show the version of libxml and libxslt used --verbose or -v: show logs of what's happening --output file or -o file: save to a given file --timing: display the time used --repeat: run the transformation 20 times --debug: dump the tree of the result instead --dumpextensions: dump the registered extension elements and functions t o stdout --novalid skip the Dtd loading phase --nodtdattr do not default attributes from the DTD --noout: do not dump the result --maxdepth val : increase the maximum depth --maxparserdepth val : increase the maximum parser depth --html: the input document is(are) an HTML file(s) --param name value : pass a (parameter,value) pair value is an UTF8 XPath expression. string values must be quoted like "'string'" or use stringparam to avoid it --stringparam name value : pass a (parameter, UTF8 string value) pair --path 'paths': provide a set of paths for resources --nonet : refuse to fetch DTDs or entities over network --nowrite : refuse to write to any file or resource --nomkdir : refuse to create directories --writesubtree path : allow file write only with the path subtree --catalogs : use SGML catalogs from $SGML_CATALOG_FILES otherwise XML Catalogs starting from file:///etc/xml/catalog are activated by default --xinclude : do XInclude processing on document intput --load-trace : print trace of all external entites loaded --profile or --norman : dump profiling informations Project libxslt home page: http://xmlsoft.org/XSLT/ To report bugs and get help: http://xmlsoft.org/XSLT/bugs.html Same goes for doxygen $ doxygen Doxyfile not found and no input file specified! Doxygen version 1.4.7 Copyright Dimitri van Heesch 1997-2006 You can use doxygen in a number of ways: 1) Use doxygen to generate a template configuration file: doxygen [-s] -g [configName] If - is used for configName doxygen will write to standard output. 2) Use doxygen to update an old configuration file: doxygen [-s] -u [configName] 3) Use doxygen to generate documentation using an existing configuration file: doxygen [configName] If - is used for configName doxygen will read from standard input. 4) Use doxygen to generate a template style sheet file for RTF, HTML or Latex. RTF: doxygen -w rtf styleSheetFile HTML: doxygen -w html headerFile footerFile styleSheetFile [configFile] LaTeX: doxygen -w latex headerFile styleSheetFile [configFile] 5) Use doxygen to generate an rtf extensions file RTF: doxygen -e rtf extensionsFile If -s is specified the comments in the config file will be omitted. If configName is omitted `Doxyfile' will be used as a default. ************ I don't get any .html files created in the html directory. So now I'm stuck. Please help. FYI - a couple of comments on getting/started.html (very strange name!) 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 presumed the former. I've double checked this like so: $ ls "$DOCBOOK_XSL_DIR" AUTHORS RELEASE-NOTES.txt javahelp BUGS RELEASE-NOTES.xml lib COPYING TODO manpages ChangeHistory.xml.zip VERSION params ChangeLog.xml catalog.xml profiling INSTALL common slides LOG eclipse template NEWS extensions test.sh NEWS.html fo tools NEWS.xml html uninstall.sh README htmlhelp website RELEASE-NOTES.html images wordml RELEASE-NOTES.pdf install.sh xhtml $ ls "$DOCBOOK_DTD_DIR" ChangeLog catalog.xml dbhierx.mod docbook.cat soextblx.dtd README dbcentx.mod dbnotnx.mod docbookx.dtd calstblx.dtd dbgenent.mod dbpoolx.mod ent $ So what am I missing? Robert Ramey
Robert Ramey wrote:
$ bjam --v2 warning: Python location is not configured warning: the Boost.Python library won't be built Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). warning: no toolsets are configured. warning: you won't be able to build C++ programs. warning: please consult the documentation at warning: http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html
You need to follow that link and activate at least one compiler in your user-config.jam John.
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" compilation error: file file:///C%3A/BoostHead/tools/boostbook/xsl/html.xsl li 8 element import xsl:import : unable to load http://docbook.sourceforge.net/release/xsl/current .... set XML_CATALOG_FILES=..\bin.v2\doc\msvc-7.1\debug/catalog.xml "xsltproc" --stringparam boost.libraries ../../libs/libraries.htm --path ..\bin .v2\libs\foreach\doc\msvc-7.1\debug --path ..\bin.v2\libs\functional\hash\doc\ms vc-7.1\debug --path ..\bin.v2\libs\math\doc\msvc-7.1\debug --path ..\bin.v2\libs \static_assert\doc\msvc-7.1\debug --path ..\bin.v2\libs\tr1\doc\msvc-7.1\debug - -path ..\bin.v2\libs\type_traits\doc\msvc-7.1\debug --path ..\bin.v2\libs\typeof \doc\msvc-7.1\debug --path ..\bin.v2\libs\xpressive\doc\msvc-7.1\debug --path .. \bin.v2\more\whos_using\msvc-7.1\debug --path ..\bin.v2\tools\jam\doc\msvc-7.1\d ebug\link-static --path ..\bin.v2\tools\quickbook\doc\msvc-7.1\debug\link-static --xinclude -o "html/" "C:\BoostHead\tools\boostbook\xsl\html.xsl" "..\bin.v2\do c\msvc-7.1\debug\boost.docbook" ...failed xslt-xsltproc-dir html\HTML.manifest... ...failed updating 1 target... I don't find any *.html files in the html directory. So, I'm stuck again. Robert Ramey John Maddock wrote:
Robert Ramey wrote:
$ bjam --v2 warning: Python location is not configured warning: the Boost.Python library won't be built Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). warning: no toolsets are configured. warning: you won't be able to build C++ programs. warning: please consult the documentation at warning: http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html
You need to follow that link and activate at least one compiler in your user-config.jam
John.
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.
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.
Robert Ramey wrote:
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.
I think the blog by Julio M. Merino Vidal is more enlightening than our own "official" docs: http://tinyurl.com/nc65b. HTH. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net
That helped - I wasn't blowing away bin.v2 after changiing user-config.jam.
Now I'm down to :
$ bjam --v2
warning: Python location is not configured
warning: the Boost.Python library won't be built
Building Boost.Regex with the optional Unicode/ICU support disabled.
Please refer to the Boost.Regex documentation for more information
(and if you don't know what ICU is then you probably don't need it).
...patience...
...found 1100 targets...
...updating 2 targets...
xslt-xsltproc ..\bin.v2\doc\msvc-7.1\debug\boost.docbook
../bin.v2/doc/msvc-7.1/debug/catalog.xml:0: element rewriteURI: Catalog
error :
rewriteURI entry 'rewritePrefix' broken ?: file:///Program
Files/docbook/xsl/
set XML_CATALOG_FILES=..\bin.v2\doc\msvc-7.1\debug/catalog.xml
"xsltproc" --stringparam boost.libraries ../../libs/libraries.htm --path
..\bin
.v2\libs\foreach\doc\msvc-7.1\debug --path
..\bin.v2\libs\functional\hash\doc\ms
vc-7.1\debug --path ..\bin.v2\libs\math\doc\msvc-7.1\debug --path
..\bin.v2\libs
\static_assert\doc\msvc-7.1\debug --path
..\bin.v2\libs\tr1\doc\msvc-7.1\debug -
-path ..\bin.v2\libs\type_traits\doc\msvc-7.1\debug --path
..\bin.v2\libs\typeof
\doc\msvc-7.1\debug --path
..\bin.v2\libs\xpressive\doc\msvc-7.1\debug --path ..
\bin.v2\more\whos_using\msvc-7.1\debug --path
..\bin.v2\tools\jam\doc\msvc-7.1\d
ebug\link-static --path
..\bin.v2\tools\quickbook\doc\msvc-7.1\debug\link-static
--xinclude -o "..\bin.v2\doc\msvc-7.1\debug\boost.docbook"
"C:\BoostHead\tools\
boostbook\xsl\docbook.xsl" "src\boost.xml"
...failed xslt-xsltproc ..\bin.v2\doc\msvc-7.1\debug\boost.docbook...
...skipped <phtml>HTML.manifest for lack of
Robert Ramey wrote:
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.
I think the blog by Julio M. Merino Vidal is more enlightening than our own "official" docs: http://tinyurl.com/nc65b.
HTH.
Regards,
participants (3)
-
Joel de Guzman -
John Maddock -
Robert Ramey