I am continuing to have problems building documentation - on the 1.34.1 branch, I keep getting bjam errors saying that boost.book is not initialized even though it is quite clearly present in the user-config.jam file. I probably just need to post a support request - it shouldn't be this hard to keep stuff functional...
Ah ha. Boostbook needs to be initialized before doxygen. Check the order in your user-config.jam
I wish it was that simple... Here's my user-config.jam : # # Boost.Build Configuration # Automatically generated by Boost configure # Compiler configuration using darwin ; using mpi ; using xsltproc : "/usr/bin/xsltproc" ; using boostbook : "/usr/local/docbook/docbook-xsl-1.73.0" : "/usr/local/docbook/docbook-xml-4" ; using doxygen : "/usr/local/bin/doxygen" ; I get weird and discrepant results depending on whether I use 1.34.1 or CVS-HEAD. In the former case, is get the following error about boostbook initialization when I run bjam --v2 --toolset=darwin html in the libs/units/doc directory: warn: Unable to construct ./standalone error: the boostbook module is not initialized error: you've attempted to use the 'doxygen' toolset, error: which requires Boost.Book, error: but never initialized Boost.Book. error: Hint: add 'using boostbook ;' to your user-config.jam I have no idea what ./standalone is or is supposed to do. In the latter case, bjam appears to run OK, though the warning about ./ standalone is still there. However, as far as I can tell, there is no html output. I do get this : quickbook.quickbook-to-boostbook ../../../bin.v2/libs/units/doc/ darwin/debug/units.xml Generating Output File: ../../../bin.v2/libs/units/doc/darwin/debug/ units.xml and units.xml is being regenerated, but I don't get any html output. Argh. In all cases, I delete the bin.v2 directory before running bjam, and the paths specified are correct (xsltproc and doxygen are actually in the default path, but it doesn't appear to matter whether I have the path or not). Anyone have any ideas? Matthias
AMDG Matthias Schabel <boost <at> schabel-family.org> writes:
warn: Unable to construct ./standalone error: the boostbook module is not initialized error: you've attempted to use the 'doxygen' toolset, error: which requires Boost.Book, error: but never initialized Boost.Book. error: Hint: add 'using boostbook ;' to your user-config.jam
I have no idea what ./standalone is or is supposed to do.
./standalone is the name of the main target that generates the html. (check the Jamfile.v2) In Christ, Steven Watanabe
warn: Unable to construct ./standalone
./standalone is the name of the main target that generates the html. (check the Jamfile.v2)
I get the same error when I try to build docs for Boost.MPI (from CVS- HEAD), so I don't think the problem is with the Boost.Units documentation per se. This is the kind of stuff that makes me less than lukewarm on the homegrown Boost documentation tools - doxygen alone may not be as flexible or produce output that is as pretty, but at least it worked reliably... There are few things that are less fun than writing documentation, but having to deal with faulty tools for documentation is one of them. Matthias
Matthias Schabel wrote:
warn: Unable to construct ./standalone
./standalone is the name of the main target that generates the html. (check the Jamfile.v2)
I get the same error when I try to build docs for Boost.MPI (from CVS- HEAD), so I don't think the problem is with the Boost.Units documentation per se. This is the kind of stuff that makes me less than lukewarm on the homegrown Boost documentation tools - doxygen alone may not be as flexible or produce output that is as pretty, but at least it worked reliably... There are few things that are less fun than writing documentation, but having to deal with faulty tools for documentation is one of them.
:-( MPI docs build OK for me, here's what my user-config.jam looks like in case it helps: using xsltproc : "C:/download/open/xml/bin/xsltproc-win32/xsltproc.exe" ; using boostbook : "C:/download/open/xml/docbook-xsl-snapshot" #"C:/download/open/xml/docbook-xsl" : "C:/download/open/xml/docbook-xml" ; using fop : #C:/download/open/xml/fop-0.93/fop.bat #C:/download/open/xml/fop-0.20.5/fop.bat C:/Progra~1/xep/xep.bat : C:/PROGRA~1/Java/j2re1.4.2_12 ; using quickbook : "C:/download/open/xml/bin/quickbook.exe" ; using doxygen : "C:/Program Files/doxygen/bin/doxygen.exe" ; I tried building the current SVN/sandbox docs for Boost.Units but get the following error: xslt-xsltproc ..\..\..\bin.v2\libs\units\doc\msvc-8.0\debug\threading-multi\unit s_reference-xml.boostbook warning: failed to load external entity "Reference" cannot parse Reference set XML_CATALOG_FILES=..\..\..\bin.v2\libs\units\doc\msvc-8.0\debug\threading- multi/catalog.xml "C:/download/open/xml/bin/xsltproc-win32/xsltproc.exe" --stringparam boost.doxy gen.reftitle ""Units Reference"" --xinclude -o "..\..\..\bin.v2\libs\units\doc\m svc-8.0\debug\threading-multi\units_reference-xml.boostbook" "c:\data\boost\boos t\trunk\tools\boostbook\xsl\doxygen\doxygen2boostbook.xsl" "..\..\..\bin.v2\libs \units\doc\msvc-8.0\debug\threading-multi\units_reference-xml.doxygen" Not sure what "Reference" is? HTH, John.
Not sure what "Reference" is?
Dunno... the build system for building the docs seems to be very fragile. I've never actually gotten it to work. For instance, boost book has been busted with --layout=system since January. See: http://archive.netbsd.se/?ml=boost-build&a=2007-01&m=3001156 If building this is so problematic, can somebody at least put the generated doc html files for 1.34.1 on the web? -benjamin
Benjamin Kosnik wrote:
Not sure what "Reference" is?
Dunno... the build system for building the docs seems to be very fragile. I've never actually gotten it to work.
For instance, boost book has been busted with --layout=system since January.
Not sure why you would want the --layout=system option - I don't think it has any effect on the doc build. In any case this does build OK for me on Win32, with RC_1_34_0
See: http://archive.netbsd.se/?ml=boost-build&a=2007-01&m=3001156
If building this is so problematic, can somebody at least put the generated doc html files for 1.34.1 on the web?
As in www.boost.org ? Or as in the docs present in the zip you download from the usual download page? John.
For instance, boost book has been busted with --layout=system since January.
Not sure why you would want the --layout=system option - I don't think it has any effect on the doc build.
It's the way the rest of the build is configured. I agree that this shouldn't actually make a difference for building documentation.
If building this is so problematic, can somebody at least put the generated doc html files for 1.34.1 on the web?
As in www.boost.org ? Or as in the docs present in the zip you download from the usual download page?
I don't see boost-doc-html for 1.34.1 up. Am I missing something? -benjamin
Benjamin Kosnik wrote:
As in www.boost.org ? Or as in the docs present in the zip you download from the usual download page?
I don't see boost-doc-html for 1.34.1 up. Am I missing something?
Ah I see - we didn't generate a doc's only zip for the last release - all the docs are present in the full download though at http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041 I'm not really sure of the value of generating a docs only zip - given that the boostbook generated docs cover only a subset of boost. John.
I get the same error when I try to build docs for Boost.MPI (from CVS- HEAD), so I don't think the problem is with the Boost.Units documentation per se. This is the kind of stuff that makes me less than lukewarm on the homegrown Boost documentation tools - doxygen alone may not be as flexible or produce output that is as pretty, but at least it worked reliably... There are few things that are less fun than writing documentation, but having to deal with faulty tools for documentation is one of them.
:-(
MPI docs build OK for me, here's what my user-config.jam looks like in case it helps:
John, Thanks for the info - the instructions on manual configuration in the Boost.Book documentation appear to be incorrect. Reinstalling from scratch and using the auto-configure script appears to have solved the problem. This toolchain is really brittle, though - in the process of getting it to work, I must have run into a half-dozen different and equally inscrutable errors... Also, while I'm grousing...why, when ./configure builds bjam does it end up in tools/ jam/src/bin.XXX? It makes zero sense to have binaries showing up in source directories AFAICS... If we want consistent documentation, it just can't be this difficult to get it to work. It almost makes Word (TM) look appealing. Almost. Crabby documenter, Matthias
AMDG John Maddock <john <at> johnmaddock.co.uk> writes:
I tried building the current SVN/sandbox docs for Boost.Units but get the following error:
<snip>
http://svn.boost.org/trac/boost/ticket/1165 In Christ, Steven Watanabe
participants (4)
-
Benjamin Kosnik -
John Maddock -
Matthias Schabel -
Steven Watanabe