Boost.Thread and BoostBook

The Boost.Thread documentation in the thread_dev branch in CVS appears to have been partially converted to BoostBook format. I've been hoping to build it to take a look and see what state it's in currently, then update pieces as I work on them. As a preliminary step, I've been trying to follow the instructions at http://www.boost.org/doc/html/boostbook.getting.started.html for building the Boost documentation that has already been converted to BoostBook but am getting errors. As I'm not very fluent yet with either bjam or BoostBook, I'd appreciate some help. FYI: I'm trying to use it on WinXP Pro without CygWin. I've already downloaded libxml, libxslt, and iconv libraries and made sure all of the pre-built utilities are on the system path. I've downloaded source for bjam and built it just today. The problem is that when I run "bjam --v2" I get the output at the end of this message and nothing builds. Any suggestions? Mike C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2/tools\boostbook.jam:321: in construct warning: rulename $(base-target).depends expands to empty string C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2/build\targets.jam:955: in object(boostbook-target-class)@1.generate C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2/build\targets.jam:521: in generate-really C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2/build\targets.jam:494: in object(main-target)@1.generate C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2/build\targets.jam:179: in object(project-target)@9.generate C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2\build-system.jam:160: in load C:\VSSNZ\Libraries\Boost\boost_cvs\boost_ssh\tools\build\v2/kernel\modules.jam:259: in import C:\VSSNZ\Libraries\Boost\boost_cvs\boost_ssh\tools\build\v2/kernel/bootstrap.jam:120: in boost-build C:\VSSNZ\Libraries\Boost\boost_cvs\boost_ssh\boost-build.jam:12: in module scope C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2/tools\boostbook.jam:325: in construct warning: rulename $(target).set-path expands to empty string C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2/build\targets.jam:955: in object(boostbook-target-class)@1.generate C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2/build\targets.jam:521: in generate-really C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2/build\targets.jam:494: in object(main-target)@1.generate C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2/build\targets.jam:179: in object(project-target)@9.generate C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2\build-system.jam:160: in load C:\VSSNZ\Libraries\Boost\boost_cvs\boost_ssh\tools\build\v2/kernel\modules.jam:259: in import C:\VSSNZ\Libraries\Boost\boost_cvs\boost_ssh\tools\build\v2/kernel/bootstrap.jam:120: in boost-build C:\VSSNZ\Libraries\Boost\boost_cvs\boost_ssh\boost-build.jam:12: in module scope C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2/build\targets.jam:1060: in check-for-unused-sources from module object(boostbook-target-class)@1 warning: Unused source { src/boost.XML } in main target ./doc C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2/build\targets.jam:957: in object(boostbook-target-class)@1.generate from module object(boostbook-target-class)@1 C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2/build\targets.jam:521: in generate-really from module object(main-target)@1 C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2/build\targets.jam:494: in object(main-target)@1.generate from module object(main-target)@1 C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2/build\targets.jam:179: in object(project-target)@9.generate from module object(project-target)@9 C:/VSSNZ/Libraries/Boost/boost_cvs/boost_ssh/tools/build/v2\build-system.jam:160: in load from module build-system C:\VSSNZ\Libraries\Boost\boost_cvs\boost_ssh\tools\build\v2/kernel\modules.jam:259: in import from module modules C:\VSSNZ\Libraries\Boost\boost_cvs\boost_ssh\tools\build\v2/kernel/bootstrap.jam:120: in boost-build from module C:\VSSNZ\Libraries\Boost\boost_cvs\boost_ssh\boost-build.jam:12: in module scope from module BoostBook warning: no DocBook XSL directory specified. If you have the DocBook XSL stylesheets installed, please set DOCBOOK_XSL_DIR to the stylesheet directory on either the command line (via -sDOCBOOK_XSL_DIR=...) or in a Boost.Jam configuration file. The DocBook XSL stylesheets are available here: http://docbook.sourceforge.net/ Stylesheets will be downloaded on-the-fly (very slow!) BoostBook warning: no DocBook DTD directory specified. If you have the DocBook DTD installed, please set DOCBOOK_DTD_DIR to the DTD directory on either the command line (via -sDOCBOOK_DTD_DIR=...) or in a Boost.Jam configuration file. The DocBook DTD is available here: http://www.oasis-open.org/docbook/xml/4.2/index.shtml The DTD will be downloaded on-the-fly (very slow!) ...found 3 targets...

On Friday 26 March 2004 05:41 pm, Michael Glassford wrote:
As a preliminary step, I've been trying to follow the instructions at http://www.boost.org/doc/html/boostbook.getting.started.html for building the Boost documentation that has already been converted to BoostBook but am getting errors. As I'm not very fluent yet with either bjam or BoostBook, I'd appreciate some help.
Sure!
FYI: I'm trying to use it on WinXP Pro without CygWin. I've already downloaded libxml, libxslt, and iconv libraries and made sure all of the pre-built utilities are on the system path. I've downloaded source for bjam and built it just today.
It should work on that platform.
The problem is that when I run "bjam --v2" I get the output at the end of this message and nothing builds. Any suggestions?
What does your user-config.jam look like? Doug

Douglas Gregor wrote:
On Friday 26 March 2004 05:41 pm, Michael Glassford wrote:
The problem is that when I run "bjam --v2" I get the output at the end of this message and nothing builds. Any suggestions?
What does your user-config.jam look like?
Unchanged from cvs. I didn't see anything telling me to change it except in the "Configuring local DocBook XSL and TDD distributions", "Configuring Apache FOP for PostScript/PDF Output", and "Configuring Doxygen for Documentation Extraction", and I didn't do any of these things. Did I miss something?
Doug _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

On Friday 26 March 2004 09:02 pm, Michael Glassford wrote:
Douglas Gregor wrote:
On Friday 26 March 2004 05:41 pm, Michael Glassford wrote:
The problem is that when I run "bjam --v2" I get the output at the end of this message and nothing builds. Any suggestions?
What does your user-config.jam look like?
Unchanged from cvs. I didn't see anything telling me to change it except in the "Configuring local DocBook XSL and TDD distributions", "Configuring Apache FOP for PostScript/PDF Output", and "Configuring Doxygen for Documentation Extraction", and I didn't do any of these things. Did I miss something?
Hmm, no, it looks like the default config isn't quite right. You'll need to edit user-config.jam (or whichever config file you please) and uncomment the line "using boostbook ;" to get it working. Doug

Douglas Gregor wrote:
On Friday 26 March 2004 09:02 pm, Michael Glassford wrote:
Douglas Gregor wrote:
On Friday 26 March 2004 05:41 pm, Michael Glassford wrote:
The problem is that when I run "bjam --v2" I get the output at the end of this message and nothing builds. Any suggestions?
What does your user-config.jam look like?
Unchanged from cvs. I didn't see anything telling me to change it except in the "Configuring local DocBook XSL and TDD distributions", "Configuring Apache FOP for PostScript/PDF Output", and "Configuring Doxygen for Documentation Extraction", and I didn't do any of these things. Did I miss something?
Hmm, no, it looks like the default config isn't quite right. You'll need to edit user-config.jam (or whichever config file you please) and uncomment the line "using boostbook ;" to get it working.
Well, that gets me a little farther, but now xsltproc.exe crashes. The output is attached to the end of the message. I noticed it was defaulting to gcc, which I don't have installed, so I also added "using msvc ;" to user-config.jam. It warns me that it found two versions, 6 and 7.1, and that it will use 7.1, but still crashes. If I instead add "using msvc : : c:/msvs6/vc98/bin ;" to force it to use MSVC6 (because version 7.1 unfortunately isn't my main compiler, though we're thankfully finally moving that way), I get the same result. Any ideas about this, now? Mike XXX ...found 51 targets... ...updating 2 targets... xslt-xsltproc bin\gcc\debug\boost.docbook set XML_CATALOG_FILES=catalog.xml "xsltproc" --xinclude -o "bin\gcc\debug\boost.docbook" "C:\VSSNZ\Libraries\Boost\boost_cvs\boost_ssh\tools\boostbook\xsl\docbook.xsl" "src\boost.xml" ...failed xslt-xsltproc bin\gcc\debug\boost.docbook... ...skipped <phtml>HTML.manifest for lack of <pbin\gcc\debug>boost.docbook... ...failed updating 1 target... ...skipped 1 target...

Michael Glassford wrote:
Douglas Gregor wrote:
On Friday 26 March 2004 09:02 pm, Michael Glassford wrote:
Douglas Gregor wrote:
On Friday 26 March 2004 05:41 pm, Michael Glassford wrote:
The problem is that when I run "bjam --v2" I get the output at the end of this message and nothing builds. Any suggestions?
What does your user-config.jam look like?
Unchanged from cvs. I didn't see anything telling me to change it except in the "Configuring local DocBook XSL and TDD distributions", "Configuring Apache FOP for PostScript/PDF Output", and "Configuring Doxygen for Documentation Extraction", and I didn't do any of these things. Did I miss something?
Hmm, no, it looks like the default config isn't quite right. You'll need to edit user-config.jam (or whichever config file you please) and uncomment the line "using boostbook ;" to get it working.
Perhaps this should be documented on the BoostBook "Getting Started" page? Along with the fact (if it's still true) that you have to delete catalog.xml for changes to the configuration file to take effect, and that if any existing .html files in the doc\html directory are read-only, (e.g. because cvs, or perhaps Tortoise CVS, makes them read only when you do a cvs checkout), BoostBook won't replace them?
Well, that gets me a little farther, but now xsltproc.exe crashes. The output is attached to the end of the message.
I re-downloaded and reinstalled libxslt and related libraries and now it seems to be working. No doubt I'll have some questions about how to use it, but that will have to wait until I actually do. Thanks for the help, Mike

On Monday 29 March 2004 08:22 am, Michael Glassford wrote:
Hmm, no, it looks like the default config isn't quite right. You'll need to edit user-config.jam (or whichever config file you please) and uncomment the line "using boostbook ;" to get it working.
Perhaps this should be documented on the BoostBook "Getting Started" page?
Either it should be documented or fixed. I'll do one of the above Real Soon Now.
Along with the fact (if it's still true) that you have to delete catalog.xml for changes to the configuration file to take effect,
Yep, that's a really annoying, persistent problem.
and that if any existing .html files in the doc\html directory are read-only, (e.g. because cvs, or perhaps Tortoise CVS, makes them read only when you do a cvs checkout), BoostBook won't replace them?
Hmmm, right. All of these could (should) be fixed, but I should document them until they do get fixed.
Well, that gets me a little farther, but now xsltproc.exe crashes. The output is attached to the end of the message.
I re-downloaded and reinstalled libxslt and related libraries and now it seems to be working. No doubt I'll have some questions about how to use it, but that will have to wait until I actually do.
Interesting. Glad you got it up and running. Sorry it wasn't quite so smooth. Doug
participants (2)
-
Douglas Gregor
-
Michael Glassford