[boostbook] Building Boost documentation

[Edward Diener-3]

Because I wanted to read documentation on some of the new libraries in
the latest Boost SVN repository, which existed only in XML format, it
was time to go through the annual rite of attempting to use Doug
Gregor's excellent documention of "The Boostbook Documentation Format"
in order to setup the documentation system to generate documentation
using bjam. Although Mr. Gregor's documentation is extremely good, I
have never been completely successful in the past, but I had my fingers
crossed in hopeful expectation this time. I am doing this on Windows so
I have to set things up manually.

1) I downloaded xsltproc and doxygen successfully, and "installed" them
into appropriate directories and, to make things easy for myself, put
those directories in my PATH.

2) After making sure I had no .jam file of any kind in my home directory
I went to the \tools\build\v2\user-config,jam in the directory in which
the latest  Boost Subversion resides, and added the line:

using xsltproc ;

3) I downloaded the latest XSL stylesheets and Docbook DTD and put them
in their own separate directies, "E:\Utilities\docbook-xsl-1.73.2" and
"E:\Utilities\docbook-dtd-4.2".

4) I added to my user-config.jam the lines:

#  BoostBook configuration
using boostbook
     : E:/Utilities/docbook-xsl-1.73.2
     : E:/Utilities/docbook-dtd-4.2
     ;

5) Now further following instructions to test out my installation so far
I went to the \libs\function\doc after copying boostbook.css from the
\doc\html directory, and tried the bjam command. My result is:

"warning: Graph library does not contain optional GraphML reader.
note: to enable GraphML support, set EXPAT_INCLUDE and EXPAT_LIBPATH to the
note: directories containing the Expat headers and libraries, respectively.
warning: skipping optional Message Passing Interface (MPI) library.
note: to enable MPI support, add "using mpi ;" to user-config.jam.
note: to suppress this message, pass "--without-mpi" to bjam.
note: otherwise, you can safely ignore this message.
Building Boost.Regex with the optional Unicode/ICU support disabled.
Please refer to the Boost.Regex documentation for more information
(don't panic: this is a strictly optional feature).
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/tools\boostbook.jam:300:
    in object(boostbook-generator)@326.run
warning: rulename $(base-target).depends expands to empty string
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:840
: in try-one-generator-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:902
: in try-one-generator
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:111
0: in construct-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:118
6: in generators.construct
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:1398:
in construct
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:1242:
in object(typed-target)@327.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:765:

in generate-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:738:

in object(main-target)@331.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:255:

in object(project-target)@325.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2\build-system.jam:402:

in load
E:\Utilities\BoostLibraries\boost_1_34_0\tools\build\v2/kernel\modules.jam:261:
in import
E:\Utilities\BoostLibraries\boost_1_34_0\tools\build\v2/kernel/bootstrap.jam:132
: in boost-build
E:\Programming\Version Control\Subversion\Boost\boost-build.jam:9: in
module scope
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/tools\boostbook.jam:307:
in object(boostbook-generator)@326.run
warning: rulename $(target[2]).set-path expands to empty string
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:840
: in try-one-generator-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:902
: in try-one-generator
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:111
0: in construct-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:118
6: in generators.construct
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:1398:
in construct
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:1242:
in object(typed-target)@327.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:765:

in generate-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:738:

in object(main-target)@331.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:255:

in object(project-target)@325.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2\build-system.jam:402:

in load
E:\Utilities\BoostLibraries\boost_1_34_0\tools\build\v2/kernel\modules.jam:261:
in import
E:\Utilities\BoostLibraries\boost_1_34_0\tools\build\v2/kernel/bootstrap.jam:132
: in boost-build
E:\Programming\Version Control\Subversion\Boost\boost-build.jam:9: in
module scope
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/tools\boostbook.jam:308:
in object(boostbook-generator)@326.run
warning: rulename $(target[2]).depends expands to empty string
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:840
: in try-one-generator-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:902
: in try-one-generator
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:111
0: in construct-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:118
6: in generators.construct
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:1398:
in construct
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:1242:
in object(typed-target)@327.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:765:

in generate-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:738:

in object(main-target)@331.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:255:

in object(project-target)@325.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2\build-system.jam:402:

in load
E:\Utilities\BoostLibraries\boost_1_34_0\tools\build\v2/kernel\modules.jam:261:
in import
E:\Utilities\BoostLibraries\boost_1_34_0\tools\build\v2/kernel/bootstrap.jam:132
: in boost-build
E:\Programming\Version Control\Subversion\Boost\boost-build.jam:9: in
module scope
warn: Unable to construct ./function-doc
...found 1 target..."

I have no doubt done something wrong, but I have no idea what.
Anybody have any clues ?

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Edward Diener wrote:

> Because I wanted to read documentation on some of the new libraries in
> the latest Boost SVN repository, which existed only in XML format, it
> was time to go through the annual rite of attempting to use Doug
> Gregor's excellent documention of "The Boostbook Documentation Format"
> in order to setup the documentation system to generate documentation
> using bjam. Although Mr. Gregor's documentation is extremely good, I
> have never been completely successful in the past, but I had my fingers
> crossed in hopeful expectation this time. I am doing this on Windows so
> I have to set things up manually.
>
> 1) I downloaded xsltproc and doxygen successfully, and "installed" them
> into appropriate directories and, to make things easy for myself, put
> those directories in my PATH.
>
> 2) After making sure I had no .jam file of any kind in my home directory
> I went to the \tools\build\v2\user-config,jam in the directory in which
> the latest  Boost Subversion resides, and added the line:
>
> using xsltproc ;
>
> 3) I downloaded the latest XSL stylesheets and Docbook DTD and put them
> in their own separate directies, "E:\Utilities\docbook-xsl-1.73.2" and
> "E:\Utilities\docbook-dtd-4.2".
>
> 4) I added to my user-config.jam the lines:
>
> #  BoostBook configuration
> using boostbook
>      : E:/Utilities/docbook-xsl-1.73.2
>      : E:/Utilities/docbook-dtd-4.2
>      ;
>
> 5) Now further following instructions to test out my installation so far
> I went to the \libs\function\doc after copying boostbook.css from the
> \doc\html directory, and tried the bjam command. My result is:
>
> "warning: Graph library does not contain optional GraphML reader.
> note: to enable GraphML support, set EXPAT_INCLUDE and EXPAT_LIBPATH to
> the note: directories containing the Expat headers and libraries,
> respectively. warning: skipping optional Message Passing Interface (MPI)
> library. note: to enable MPI support, add "using mpi ;" to
> user-config.jam. note: to suppress this message, pass "--without-mpi" to
> bjam. note: otherwise, you can safely ignore this message.
> Building Boost.Regex with the optional Unicode/ICU support disabled.
> Please refer to the Boost.Regex documentation for more information
> (don't panic: this is a strictly optional feature).
> E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/tools\boostbook.jam:300:
>     in object(boostbook-generator)@326.run
> warning: rulename $(base-target).depends expands to empty string

1. Add --debug-generators option to bjam and send the the output.
2. Try adding

        using doxygen ;

to user-config.jam

Thanks,
Volodya


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[Edward Diener-3]

Vladimir Prus wrote:

> Edward Diener wrote:
>
>> Because I wanted to read documentation on some of the new libraries in
>> the latest Boost SVN repository, which existed only in XML format, it
>> was time to go through the annual rite of attempting to use Doug
>> Gregor's excellent documention of "The Boostbook Documentation Format"
>> in order to setup the documentation system to generate documentation
>> using bjam. Although Mr. Gregor's documentation is extremely good, I
>> have never been completely successful in the past, but I had my fingers
>> crossed in hopeful expectation this time. I am doing this on Windows so
>> I have to set things up manually.
>>
>> 1) I downloaded xsltproc and doxygen successfully, and "installed" them
>> into appropriate directories and, to make things easy for myself, put
>> those directories in my PATH.
>>
>> 2) After making sure I had no .jam file of any kind in my home directory
>> I went to the \tools\build\v2\user-config,jam in the directory in which
>> the latest  Boost Subversion resides, and added the line:
>>
>> using xsltproc ;
>>
>> 3) I downloaded the latest XSL stylesheets and Docbook DTD and put them
>> in their own separate directies, "E:\Utilities\docbook-xsl-1.73.2" and
>> "E:\Utilities\docbook-dtd-4.2".
>>
>> 4) I added to my user-config.jam the lines:
>>
>> #  BoostBook configuration
>> using boostbook
>>      : E:/Utilities/docbook-xsl-1.73.2
>>      : E:/Utilities/docbook-dtd-4.2
>>      ;
>>
>> 5) Now further following instructions to test out my installation so far
>> I went to the \libs\function\doc after copying boostbook.css from the
>> \doc\html directory, and tried the bjam command. My result is:
>>
>> "warning: Graph library does not contain optional GraphML reader.
>> note: to enable GraphML support, set EXPAT_INCLUDE and EXPAT_LIBPATH to
>> the note: directories containing the Expat headers and libraries,
>> respectively. warning: skipping optional Message Passing Interface (MPI)
>> library. note: to enable MPI support, add "using mpi ;" to
>> user-config.jam. note: to suppress this message, pass "--without-mpi" to
>> bjam. note: otherwise, you can safely ignore this message.
>> Building Boost.Regex with the optional Unicode/ICU support disabled.
>> Please refer to the Boost.Regex documentation for more information
>> (don't panic: this is a strictly optional feature).
>> E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/tools\boostbook.jam:300:
>>     in object(boostbook-generator)@326.run
>> warning: rulename $(base-target).depends expands to empty string
>
> 1. Add --debug-generators option to bjam and send the the output.
> 2. Try adding
>
>         using doxygen ;
>
> to user-config.jam

Adding the 'using doxygen ;' command made no difference. After adding
the --debug-geberators to the bjam command line I get:

"E:\Programming\Version Control\Subversion\Boost\libs\function\doc>bjam
--v2 --debug-generators
warning: Graph library does not contain optional GraphML reader.
note: to enable GraphML support, set EXPAT_INCLUDE and EXPAT_LIBPATH to the
note: directories containing the Expat headers and libraries, respectively.
warning: skipping optional Message Passing Interface (MPI) library.
note: to enable MPI support, add "using mpi ;" to user-config.jam.
note: to suppress this message, pass "--without-mpi" to bjam.
note: otherwise, you can safely ignore this message.
Building Boost.Regex with the optional Unicode/ICU support disabled.
Please refer to the Boost.Regex documentation for more information
(don't panic: this is a strictly optional feature).
      *** construct BOOSTBOOK_MAIN
          from { function.xml.XML }
          properties: <asynch-exceptions>off
<conditional>@Jamfile</E:/Programmin
g/Version Control/Subversion/Boost>%Jamfile</E:/Programming/Version
Control/Subv
ersion/Boost>.handle-static-runtime <debug-store>object
<debug-symbols>on <defin
e>BOOST_ALL_NO_LIB=1 <exception-handling>on <extern-c-nothrow>off
<format>html <
hardcode-dll-paths>true <host-os>windows <include>../../.. <inlining>off
<instal
l-dependencies>off <link>shared <main-target-type>BOOSTBOOK_MAIN
<midl-robust>ye
s <midl-stubless-proxy>yes <optimization>off <os>NT <pch>on
<profiling>off <pyth
on-debugging>off <python>2.5 <rtti>on <runtime-debugging>on
<runtime-link>shared
  <stdlib>native <suppress-import-lib>false
<symlink-location>project-relative <t
ag>@Jamfile</E:/Programming/Version
Control/Subversion/Boost>%Jamfile</E:/Progra
mming/Version Control/Subversion/Boost>.tag <target-os>windows
<threadapi>win32
<threading>multi <toolset-msvc:version>8.0 <toolset>msvc
<user-interface>console
  <variant>debug <warnings-as-errors>off <warnings>on
      find-viable-generators target-type= BOOSTBOOK_MAIN property-set=
msvc-8.0/d
ebug/threading-multi
      trying type BOOSTBOOK_MAIN
      there are generators for this type
      trying generator boostbook.main ( -> BOOSTBOOK_MAIN )
        is viable
      ***  1  viable generators
          *** construct DOCBOOK
              from { function.xml.XML }
              properties: <asynch-exceptions>off
<catalog>..\..\..\bin.v2\libs\fu
nction\doc\msvc-8.0\debug\threading-multi/catalog.xml
<conditional>@Jamfile</E:/
Programming/Version
Control/Subversion/Boost>%Jamfile</E:/Programming/Version Co
ntrol/Subversion/Boost>.handle-static-runtime <debug-store>object
<debug-symbols
 >on <define>BOOST_ALL_NO_LIB=1 <exception-handling>on
<extern-c-nothrow>off <for
mat>html <hardcode-dll-paths>true <host-os>windows <include>../../..
<inlining>o
ff <install-dependencies>off <link>shared
<main-target-type>BOOSTBOOK_MAIN <midl
-robust>yes <midl-stubless-proxy>yes <optimization>off <os>NT <pch>on
<profiling
 >off <python-debugging>off <python>2.5 <rtti>on <runtime-debugging>on
<runtime-l
ink>shared <stdlib>native <suppress-import-lib>false
<symlink-location>project-r
elative <tag>@Jamfile</E:/Programming/Version
Control/Subversion/Boost>%Jamfile<
/E:/Programming/Version Control/Subversion/Boost>.tag <target-os>windows
<thread
api>win32 <threading>multi <toolset-msvc:version>8.0 <toolset>msvc
<user-interfa
ce>console <variant>debug <warnings-as-errors>off <warnings>on
          find-viable-generators target-type= DOCBOOK property-set=
msvc-8.0/debu
g/threading-multi
          trying type DOCBOOK
          trying type XML
          ***  0  viable generators
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/tools\boostbook.jam:300:
  in object(boostbook-generator)@326.run
warning: rulename $(base-target).depends expands to empty string
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:840
: in try-one-generator-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:902
: in try-one-generator
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:111
0: in construct-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:118
6: in generators.construct
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:1398:
in construct
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:1242:
in object(typed-target)@327.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:765:
i
n generate-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:738:
i
n object(main-target)@331.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:255:
i
n object(project-target)@325.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2\build-system.jam:402:
in
  load
E:\Utilities\BoostLibraries\boost_1_34_0\tools\build\v2/kernel\modules.jam:261:
in import
E:\Utilities\BoostLibraries\boost_1_34_0\tools\build\v2/kernel/bootstrap.jam:132
: in boost-build
E:\Programming\Version Control\Subversion\Boost\boost-build.jam:9: in
module sco
pe
          *** construct HTMLDIR
              properties: <asynch-exceptions>off
<catalog>..\..\..\bin.v2\libs\fu
nction\doc\msvc-8.0\debug\threading-multi/catalog.xml
<conditional>@Jamfile</E:/
Programming/Version
Control/Subversion/Boost>%Jamfile</E:/Programming/Version Co
ntrol/Subversion/Boost>.handle-static-runtime <debug-store>object
<debug-symbols
 >on <define>BOOST_ALL_NO_LIB=1 <exception-handling>on
<extern-c-nothrow>off <for
mat>html <hardcode-dll-paths>true <host-os>windows <include>../../..
<inlining>o
ff <install-dependencies>off <link>shared
<main-target-type>BOOSTBOOK_MAIN <midl
-robust>yes <midl-stubless-proxy>yes <optimization>off <os>NT <pch>on
<profiling
 >off <python-debugging>off <python>2.5 <rtti>on <runtime-debugging>on
<runtime-l
ink>shared <stdlib>native <suppress-import-lib>false
<symlink-location>project-r
elative <tag>@Jamfile</E:/Programming/Version
Control/Subversion/Boost>%Jamfile<
/E:/Programming/Version Control/Subversion/Boost>.tag <target-os>windows
<thread
api>win32 <threading>multi <toolset-msvc:version>8.0 <toolset>msvc
<user-interfa
ce>console <variant>debug <warnings-as-errors>off <warnings>on
          find-viable-generators target-type= HTMLDIR property-set=
msvc-8.0/debu
g/threading-multi
          trying type HTMLDIR
          ***  0  viable generators
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/tools\boostbook.jam:307:
  in object(boostbook-generator)@326.run
warning: rulename $(target[2]).set-path expands to empty string
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:840
: in try-one-generator-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:902
: in try-one-generator
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:111
0: in construct-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:118
6: in generators.construct
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:1398:
in construct
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:1242:
in object(typed-target)@327.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:765:
i
n generate-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:738:
i
n object(main-target)@331.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:255:
i
n object(project-target)@325.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2\build-system.jam:402:
in
  load
E:\Utilities\BoostLibraries\boost_1_34_0\tools\build\v2/kernel\modules.jam:261:
in import
E:\Utilities\BoostLibraries\boost_1_34_0\tools\build\v2/kernel/bootstrap.jam:132
: in boost-build
E:\Programming\Version Control\Subversion\Boost\boost-build.jam:9: in
module sco
pe
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/tools\boostbook.jam:308:
  in object(boostbook-generator)@326.run
warning: rulename $(target[2]).depends expands to empty string
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:840
: in try-one-generator-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:902
: in try-one-generator
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:111
0: in construct-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\generators.jam:118
6: in generators.construct
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:1398:
in construct
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:1242:
in object(typed-target)@327.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:765:
i
n generate-really
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:738:
i
n object(main-target)@331.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/build\targets.jam:255:
i
n object(project-target)@325.generate
E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2\build-system.jam:402:
in
  load
E:\Utilities\BoostLibraries\boost_1_34_0\tools\build\v2/kernel\modules.jam:261:
in import
E:\Utilities\BoostLibraries\boost_1_34_0\tools\build\v2/kernel/bootstrap.jam:132
: in boost-build
E:\Programming\Version Control\Subversion\Boost\boost-build.jam:9: in
module sco
pe
      returned
        generator boostbook.main  spawned

warn: Unable to construct ./function-doc
find-viable-generators target-type= BOOSTBOOK_MAIN property-set=
msvc-8.0/debug/
threading-multi
trying type BOOSTBOOK_MAIN
there are generators for this type
trying generator boostbook.main ( -> BOOSTBOOK_MAIN )
   is viable
...found 1 target..."

Eddie

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[Edward Diener-3]

Vladimir Prus wrote:

> Edward Diener wrote:
>
>> Because I wanted to read documentation on some of the new libraries in
>> the latest Boost SVN repository, which existed only in XML format, it
>> was time to go through the annual rite of attempting to use Doug
>> Gregor's excellent documention of "The Boostbook Documentation Format"
>> in order to setup the documentation system to generate documentation
>> using bjam. Although Mr. Gregor's documentation is extremely good, I
>> have never been completely successful in the past, but I had my fingers
>> crossed in hopeful expectation this time. I am doing this on Windows so
>> I have to set things up manually.
>>
>> 1) I downloaded xsltproc and doxygen successfully, and "installed" them
>> into appropriate directories and, to make things easy for myself, put
>> those directories in my PATH.
>>
>> 2) After making sure I had no .jam file of any kind in my home directory
>> I went to the \tools\build\v2\user-config,jam in the directory in which
>> the latest  Boost Subversion resides, and added the line:
>>
>> using xsltproc ;
>>
>> 3) I downloaded the latest XSL stylesheets and Docbook DTD and put them
>> in their own separate directies, "E:\Utilities\docbook-xsl-1.73.2" and
>> "E:\Utilities\docbook-dtd-4.2".
>>
>> 4) I added to my user-config.jam the lines:
>>
>> #  BoostBook configuration
>> using boostbook
>>      : E:/Utilities/docbook-xsl-1.73.2
>>      : E:/Utilities/docbook-dtd-4.2
>>      ;
>>
>> 5) Now further following instructions to test out my installation so far
>> I went to the \libs\function\doc after copying boostbook.css from the
>> \doc\html directory, and tried the bjam command. My result is:
>>
>> "warning: Graph library does not contain optional GraphML reader.
>> note: to enable GraphML support, set EXPAT_INCLUDE and EXPAT_LIBPATH to
>> the note: directories containing the Expat headers and libraries,
>> respectively. warning: skipping optional Message Passing Interface (MPI)
>> library. note: to enable MPI support, add "using mpi ;" to
>> user-config.jam. note: to suppress this message, pass "--without-mpi" to
>> bjam. note: otherwise, you can safely ignore this message.
>> Building Boost.Regex with the optional Unicode/ICU support disabled.
>> Please refer to the Boost.Regex documentation for more information
>> (don't panic: this is a strictly optional feature).
>> E:/Utilities/BoostLibraries/boost_1_34_0/tools/build/v2/tools\boostbook.jam:300:
>>     in object(boostbook-generator)@326.run
>> warning: rulename $(base-target).depends expands to empty string
>
> 1. Add --debug-generators option to bjam and send the the output.
> 2. Try adding
>
>         using doxygen ;
>
> to user-config.jam

I have gotten further along but still an error.

"E:\Programming\Version Control\Subversion\Boost\libs\function\doc>bjam
--v2 --de
bug-generators
warning: Graph library does not contain optional GraphML reader.
note: to enable GraphML support, set EXPAT_INCLUDE and EXPAT_LIBPATH to the
note: directories containing the Expat headers and libraries, respectively.
warning: skipping optional Message Passing Interface (MPI) library.
note: to enable MPI support, add "using mpi ;" to user-config.jam.
note: to suppress this message, pass "--without-mpi" to bjam.
note: otherwise, you can safely ignore this message.
Building Boost.Regex with the optional Unicode/ICU support disabled.
Please refer to the Boost.Regex documentation for more information
(don't panic: this is a strictly optional feature).
warning: No toolsets are configured.
warning: Configuring default toolset "msvc".
warning: If the default is wrong, you may not be able to build C++ programs.
warning: Use the "--toolset=xxxxx" option to override our guess.
warning: For more configuration options, please consult
warning:
http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html

      *** construct BOOSTBOOK_MAIN
          from { function.xml.XML }
          properties: <asynch-exceptions>off
<conditional>@Jamfile</E:/Programmin
g/Version Control/Subversion/Boost>%Jamfile</E:/Programming/Version
Control/Subv
ersion/Boost>.handle-static-runtime <debug-store>object
<debug-symbols>on <defin
e>BOOST_ALL_NO_LIB=1 <doxygen.doxproc.index>no
<doxygen.processor>xsltproc <exce
ption-handling>on <extern-c-nothrow>off <format>html
<hardcode-dll-paths>true <h
ost-os>windows <include>../../.. <inlining>off <install-dependencies>off
<link>s
hared <main-target-type>BOOSTBOOK_MAIN <midl-robust>yes
<midl-stubless-proxy>yes
  <optimization>off <os>NT <pch>on <profiling>off <python-debugging>off
<python>2
.5 <rtti>on <runtime-debugging>on <runtime-link>shared <stdlib>native
<suppress-
import-lib>false <symlink-location>project-relative
<tag>@Jamfile</E:/Programmin
g/Version Control/Subversion/Boost>%Jamfile</E:/Programming/Version
Control/Subv
ersion/Boost>.tag <target-os>windows <threadapi>win32 <threading>single
<toolset
-msvc:version>8.0 <toolset>msvc <user-interface>console <variant>debug
<warnings
-as-errors>off <warnings>on
      find-viable-generators target-type= BOOSTBOOK_MAIN property-set=
msvc-8.0/d
ebug
      trying type BOOSTBOOK_MAIN
      there are generators for this type
      trying generator boostbook.main ( -> BOOSTBOOK_MAIN )
        is viable
      ***  1  viable generators
          *** construct DOCBOOK
              from { function.xml.XML }
              properties: <asynch-exceptions>off
<catalog>..\..\..\bin.v2/boostbo
ok_catalog.xml <conditional>@Jamfile</E:/Programming/Version
Control/Subversion/
Boost>%Jamfile</E:/Programming/Version
Control/Subversion/Boost>.handle-static-r
untime <debug-store>object <debug-symbols>on <define>BOOST_ALL_NO_LIB=1
<doxygen
.doxproc.index>no <doxygen.processor>xsltproc <exception-handling>on
<extern-c-n
othrow>off <format>html <hardcode-dll-paths>true <host-os>windows
<include>../..
/.. <inlining>off <install-dependencies>off <link>shared
<main-target-type>BOOST
BOOK_MAIN <midl-robust>yes <midl-stubless-proxy>yes <optimization>off
<os>NT <pc
h>on <profiling>off <python-debugging>off <python>2.5 <rtti>on
<runtime-debuggin
g>on <runtime-link>shared <stdlib>native <suppress-import-lib>false
<symlink-loc
ation>project-relative <tag>@Jamfile</E:/Programming/Version
Control/Subversion/
Boost>%Jamfile</E:/Programming/Version Control/Subversion/Boost>.tag
<target-os>
windows <threadapi>win32 <threading>single <toolset-msvc:version>8.0
<toolset>ms
vc <user-interface>console <variant>debug <warnings-as-errors>off
<warnings>on
          find-viable-generators target-type= DOCBOOK property-set=
msvc-8.0/debu
g
          trying type DOCBOOK
          there are generators for this type
          trying generator boostbook.boostbook-to-docbook ( XML -> DOCBOOK )
            is viable
          ***  1  viable generators
            ** generator boostbook.boostbook-to-docbook
            multiple:
            composing:
            SUCCESS:  {
boostbook%boostbook.boostbook-to-docbook-function.docbook
.DOCBOOK { function.xml.XML } }

          returned {
boostbook%boostbook.boostbook-to-docbook-function.docbook.DO
CBOOK { function.xml.XML } }
            generator boostbook.boostbook-to-docbook  spawned
            {
boostbook%boostbook.boostbook-to-docbook-function.docbook.DOCBOOK {
  function.xml.XML } }
            with usage requirements:
          *** construct HTMLDIR
              from {
boostbook%boostbook.boostbook-to-docbook-function.docbook.DO
CBOOK { function.xml.XML } }
              properties: <asynch-exceptions>off
<catalog>..\..\..\bin.v2/boostbo
ok_catalog.xml <conditional>@Jamfile</E:/Programming/Version
Control/Subversion/
Boost>%Jamfile</E:/Programming/Version
Control/Subversion/Boost>.handle-static-r
untime <debug-store>object <debug-symbols>on <define>BOOST_ALL_NO_LIB=1
<doxygen
.doxproc.index>no <doxygen.processor>xsltproc <exception-handling>on
<extern-c-n
othrow>off <format>html <hardcode-dll-paths>true <host-os>windows
<include>../..
/.. <inlining>off <install-dependencies>off <link>shared
<main-target-type>BOOST
BOOK_MAIN <midl-robust>yes <midl-stubless-proxy>yes <optimization>off
<os>NT <pc
h>on <profiling>off <python-debugging>off <python>2.5 <rtti>on
<runtime-debuggin
g>on <runtime-link>shared <stdlib>native <suppress-import-lib>false
<symlink-loc
ation>project-relative <tag>@Jamfile</E:/Programming/Version
Control/Subversion/
Boost>%Jamfile</E:/Programming/Version Control/Subversion/Boost>.tag
<target-os>
windows <threadapi>win32 <threading>single <toolset-msvc:version>8.0
<toolset>ms
vc <user-interface>console <variant>debug <warnings-as-errors>off
<warnings>on <
xsl:param>manifest=function-doc_HTML.manifest
          find-viable-generators target-type= HTMLDIR property-set=
msvc-8.0/debu
g
          trying type HTMLDIR
          there are generators for this type
          trying generator boostbook.docbook-to-htmldir ( DOCBOOK ->
HTMLDIR )
            is viable
          ***  1  viable generators
            ** generator boostbook.docbook-to-htmldir
            multiple:
            composing:
            SUCCESS:  {
boostbook%boostbook.docbook-to-htmldir-function-doc_HTML.
manifest.HTMLDIR {
boostbook%boostbook.boostbook-to-docbook-function.docbook.DOC
BOOK { function.xml.XML } } }

          returned {
boostbook%boostbook.docbook-to-htmldir-function-doc_HTML.man
ifest.HTMLDIR {
boostbook%boostbook.boostbook-to-docbook-function.docbook.DOCBOO
K { function.xml.XML } } }
            generator boostbook.docbook-to-htmldir  spawned
            {
boostbook%boostbook.docbook-to-htmldir-function-doc_HTML.manifest.H
TMLDIR {
boostbook%boostbook.boostbook-to-docbook-function.docbook.DOCBOOK { fun
ction.xml.XML } } }
            with usage requirements:
      returned {
boostbook%boostbook.docbook-to-htmldir-function-doc_HTML.manifes
t.HTMLDIR {
boostbook%boostbook.boostbook-to-docbook-function.docbook.DOCBOOK {
function.xml.XML } } }
        generator boostbook.main  spawned
        {
boostbook%boostbook.docbook-to-htmldir-function-doc_HTML.manifest.HTMLD
IR { boostbook%boostbook.boostbook-to-docbook-function.docbook.DOCBOOK {
functio
n.xml.XML } } }
        with usage requirements:
...found 22 targets...
...updating 1 target...
xslt-xsltproc-dir html\function-doc_HTML.manifest

   set XML_CATALOG_FILES=..\..\..\bin.v2/boostbook_catalog.xml
  "xsltproc" --stringparam manifest "function-doc_HTML.manifest"
--xinclude -o "h
tml/" "E:\Programming\Version
Control\Subversion\Boost\tools\boostbook\xsl\html.
xsl" "..\..\..\bin.v2\libs\function\doc\msvc-8.0\debug\function.docbook"

...failed xslt-xsltproc-dir html\function-doc_HTML.manifest...
...failed updating 1 target..."

What does the failure mean ?

The user-config.jam in my home directory now reads:

"# Copyright 2003, 2005 Douglas Gregor
# Copyright 2004 John Maddock
# Copyright 2002, 2003, 2004, 2007 Vladimir Prus
# Distributed under the Boost Software License, Version 1.0.
# (See accompanying file LICENSE_1_0.txt or
http://www.boost.org/LICENSE_1_0.txt)

#  This file is used to configure your Boost.Build installation.
#  You can modify this file in place, or you can place it it
#  permanent location so that it's not overwritten should you
#  get new version of Boost.Build. See:
#
#
http://boost.org/boost-build2/doc/html/bbv2/reference.html#bbv2.reference.init
#
#  for documentation about permanent location.

#  This file specifies which toolsets (C++ compilers), libraries,
#  and other tools are available.  Often, you should be able to
#  just uncomment existing example lines and adjust them to taste.
#  The complete list of supported tools, and configuration instructions
#  can be found at:
#
#    http://boost.org/boost-build2/doc/html/bbv2/reference/tools.html
#

#  This file uses Jam language syntax to describe available tools.
#  Mostly, there are 'using' lines, that contain the name of the used
#  tools, and parameters to pass to those tools -- where paremeters
#  are separated by semicolons.
#  Important syntax notes:
#
#    - Both ':' and ';' must be separated from other tokens by whitespace
#    - The '\' symbol is quote character, so when specifying Windows paths
#      it's recommended to use '/' instead, or use '\\'.
#
#  More details about syntax can be found at:
#
#
http://boost.org/boost-build2/doc/html/bbv2/advanced.html#bbv2.advanced.jam_language
#



#  GCC configuration

#  Configure gcc (default version)
#  using gcc ;

#  Configure specific gcc version, giving alternative name to use
#  using gcc : 3.2 : g++-3.2 ;

#  MSVC configuration

#  Configure msvc (default version, searched in standard location
#  and PATH).
#  using msvc ;

#  Borland configuration
#  using borland ;


#  STLPort configuration

#  Configure, specifying location of STLPort headers.
#  Libraries must be either not needed, or available to
#  the compiler by default
#  using stlport : : /usr/include/stlport ;

#  Configure, specifying locatioh of both headers and libraries
#  using stlport : : /usr/include/stlport /usr/lib ;


#  QT configuration

#  Configure, assuming QTDIR gives the installation prefix
#  using qt ;

#  Configure with explicit installation prefix
#  using qt : /usr/opt/qt ;

using xsltproc ;

#  BoostBook configuration
using boostbook
   : E:/Utilities/docbook-xsl-1.73.2
   : E:/Utilities/docbook-dtd-4.2
   ;

using doxygen ;"

Eddie

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[Rene Rivera-2]

Edward Diener wrote:

> ...updating 1 target...
> xslt-xsltproc-dir html\function-doc_HTML.manifest
>
>    set XML_CATALOG_FILES=..\..\..\bin.v2/boostbook_catalog.xml
>   "xsltproc" --stringparam manifest "function-doc_HTML.manifest"
> --xinclude -o "h
> tml/" "E:\Programming\Version
> Control\Subversion\Boost\tools\boostbook\xsl\html.
> xsl" "..\..\..\bin.v2\libs\function\doc\msvc-8.0\debug\function.docbook"
>
> ...failed xslt-xsltproc-dir html\function-doc_HTML.manifest...
> ...failed updating 1 target..."
>
> What does the failure mean ?

That's weird. Usually programs tell you why things fail. Try running the
same commands in a shell to see if you get the same problem. Or if it
gives some useful errors.


--
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[Mat Marcus-2]

On Nov 18, 2007 12:48 PM, Edward Diener <eldiener@...> wrote:

> I have gotten further along but still an error.

I don't know if this is relevant to your situation, but the error
messages you described remind me of some that Ifaced when trying build
boost documentation. In our situation, the issue had to do with
cygwin. For normal bbv2 operations, I need to use an msvc-built bjam
executable, presumably for compatibility with the pathname conventions
used by the msvc compiler toolchain. For documentation, however, my
toolchain islargely based on cygwin tools. I got a lot closer to my
goal when I  switched to using a cygwin-built bjam executable when
building documentation.

HTH,
Mat
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[Edward Diener-3]

Rene Rivera wrote:

> Edward Diener wrote:
>> ...updating 1 target...
>> xslt-xsltproc-dir html\function-doc_HTML.manifest
>>
>>    set XML_CATALOG_FILES=..\..\..\bin.v2/boostbook_catalog.xml
>>   "xsltproc" --stringparam manifest "function-doc_HTML.manifest"
>> --xinclude -o "h
>> tml/" "E:\Programming\Version
>> Control\Subversion\Boost\tools\boostbook\xsl\html.
>> xsl" "..\..\..\bin.v2\libs\function\doc\msvc-8.0\debug\function.docbook"
>>
>> ...failed xslt-xsltproc-dir html\function-doc_HTML.manifest...
>> ...failed updating 1 target..."
>>
>> What does the failure mean ?
>
> That's weird. Usually programs tell you why things fail. Try running the
> same commands in a shell to see if you get the same problem. Or if it
> gives some useful errors.

Running:

"xsltproc" --stringparam manifest "function-doc_HTML.manifest"
--xinclude -o "html/" "E:\Programming\Version
Control\Subversion\Boost\tools\boostbook\xsl\html.xsl"
"..\..\..\bin.v2\libs\function\doc\msvc-8.0\debug\function.docbook"

from the command line succeeds. I have no idea why bjam would say it
fails. What the command is supposed to do I do not know.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[Ilya Sokolov]

Edward Diener wrote:

> Rene Rivera wrote:
>> Edward Diener wrote:
>>> ...updating 1 target...
>>> xslt-xsltproc-dir html\function-doc_HTML.manifest
>>>
>>>    set XML_CATALOG_FILES=..\..\..\bin.v2/boostbook_catalog.xml
>>>   "xsltproc" --stringparam manifest "function-doc_HTML.manifest"
>>> --xinclude -o "h
>>> tml/" "E:\Programming\Version
>>> Control\Subversion\Boost\tools\boostbook\xsl\html.
>>> xsl" "..\..\..\bin.v2\libs\function\doc\msvc-8.0\debug\function.docbook"
>>>
>>> ...failed xslt-xsltproc-dir html\function-doc_HTML.manifest...
>>> ...failed updating 1 target..."
>>>
>>> What does the failure mean ?
>> That's weird. Usually programs tell you why things fail. Try running the
>> same commands in a shell to see if you get the same problem. Or if it
>> gives some useful errors.
>
> Running:
>
> "xsltproc" --stringparam manifest "function-doc_HTML.manifest"
> --xinclude -o "html/" "E:\Programming\Version
> Control\Subversion\Boost\tools\boostbook\xsl\html.xsl"
> "..\..\..\bin.v2\libs\function\doc\msvc-8.0\debug\function.docbook"
>
> from the command line succeeds.

are you sure? how did you determine that? (i think i've seen exactly
this problem already)

> I have no idea why bjam would say it
> fails. What the command is supposed to do I do not know.

1. try "bjam onehtml"
2. try another xsltproc (e.g. http://www.zlatkovic.com/libxml.en.html)

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[Edward Diener-3]

Ilya Sokolov wrote:

> Edward Diener wrote:
>> Rene Rivera wrote:
>>> Edward Diener wrote:
>>>> ...updating 1 target...
>>>> xslt-xsltproc-dir html\function-doc_HTML.manifest
>>>>
>>>>    set XML_CATALOG_FILES=..\..\..\bin.v2/boostbook_catalog.xml
>>>>   "xsltproc" --stringparam manifest "function-doc_HTML.manifest"
>>>> --xinclude -o "h
>>>> tml/" "E:\Programming\Version
>>>> Control\Subversion\Boost\tools\boostbook\xsl\html.
>>>> xsl" "..\..\..\bin.v2\libs\function\doc\msvc-8.0\debug\function.docbook"
>>>>
>>>> ...failed xslt-xsltproc-dir html\function-doc_HTML.manifest...
>>>> ...failed updating 1 target..."
>>>>
>>>> What does the failure mean ?
>>> That's weird. Usually programs tell you why things fail. Try running the
>>> same commands in a shell to see if you get the same problem. Or if it
>>> gives some useful errors.
>> Running:
>>
>> "xsltproc" --stringparam manifest "function-doc_HTML.manifest"
>> --xinclude -o "html/" "E:\Programming\Version
>> Control\Subversion\Boost\tools\boostbook\xsl\html.xsl"
>> "..\..\..\bin.v2\libs\function\doc\msvc-8.0\debug\function.docbook"
>>
>> from the command line succeeds.
>
> are you sure? how did you determine that? (i think i've seen exactly
> this problem already)

By succeed I mean that it returns no errors to stderr or stdout and
returns no error code of 1 or above.

>
>> I have no idea why bjam would say it
>> fails. What the command is supposed to do I do not know.
>
> 1. try "bjam onehtml"

What is that supposed to do ?

> 2. try another xsltproc (e.g. http://www.zlatkovic.com/libxml.en.html)

I will give it a try, but this business of trying to setup and use the
Boost documentation system, according to instructions, and failing to be
able to do so, is getting old. I think Boost should either consider
something better than this mess or get it working someday in this century.

I did get the xsltproc directly from the link in the The BoostBook
Documentation Format, and that link is at
http://www.meta-comm.com/engineering/boost/xsltproc-win32.zip. Is that
link's implementation of xsltproc broken perhaps ?

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Edward Diener wrote:

> Ilya Sokolov wrote:
>> Edward Diener wrote:
>>> Rene Rivera wrote:
>>>> Edward Diener wrote:
>>>>> ...updating 1 target...
>>>>> xslt-xsltproc-dir html\function-doc_HTML.manifest
>>>>>
>>>>>    set XML_CATALOG_FILES=..\..\..\bin.v2/boostbook_catalog.xml
>>>>>   "xsltproc" --stringparam manifest "function-doc_HTML.manifest"
>>>>> --xinclude -o "h
>>>>> tml/" "E:\Programming\Version
>>>>> Control\Subversion\Boost\tools\boostbook\xsl\html.
>>>>> xsl"
>>>>> "..\..\..\bin.v2\libs\function\doc\msvc-8.0\debug\function.docbook"
>>>>>
>>>>> ...failed xslt-xsltproc-dir html\function-doc_HTML.manifest...
>>>>> ...failed updating 1 target..."
>>>>>
>>>>> What does the failure mean ?
>>>> That's weird. Usually programs tell you why things fail. Try running
>>>> the same commands in a shell to see if you get the same problem. Or if
>>>> it gives some useful errors.
>>> Running:
>>>
>>> "xsltproc" --stringparam manifest "function-doc_HTML.manifest"
>>> --xinclude -o "html/" "E:\Programming\Version
>>> Control\Subversion\Boost\tools\boostbook\xsl\html.xsl"
>>> "..\..\..\bin.v2\libs\function\doc\msvc-8.0\debug\function.docbook"
>>>
>>> from the command line succeeds.
>>
>> are you sure? how did you determine that? (i think i've seen exactly
>> this problem already)
>
> By succeed I mean that it returns no errors to stderr or stdout and
> returns no error code of 1 or above.
>
>>
>>> I have no idea why bjam would say it
>>> fails. What the command is supposed to do I do not know.
>>
>> 1. try "bjam onehtml"
>
> What is that supposed to do ?
>
>> 2. try another xsltproc (e.g. http://www.zlatkovic.com/libxml.en.html)
>
> I will give it a try, but this business of trying to setup and use the
> Boost documentation system, according to instructions, and failing to be
> able to do so, is getting old. I think Boost should either consider
> something better than this mess or get it working someday in this century.
>
> I did get the xsltproc directly from the link in the The BoostBook
> Documentation Format, and that link is at
> http://www.meta-comm.com/engineering/boost/xsltproc-win32.zip. Is that
> link's implementation of xsltproc broken perhaps ?

In fact, that link is not necessary at least. I believe the official xstlproc
release is better bet.

- Volodya


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[Ilya Sokolov]

Edward Diener wrote:

> Ilya Sokolov wrote:
>> Edward Diener wrote:
>>> Rene Rivera wrote:
>>>> Edward Diener wrote:
>>>>> ...updating 1 target...
>>>>> xslt-xsltproc-dir html\function-doc_HTML.manifest
>>>>>
>>>>>    set XML_CATALOG_FILES=..\..\..\bin.v2/boostbook_catalog.xml
>>>>>   "xsltproc" --stringparam manifest "function-doc_HTML.manifest"
>>>>> --xinclude -o "h
>>>>> tml/" "E:\Programming\Version
>>>>> Control\Subversion\Boost\tools\boostbook\xsl\html.
>>>>> xsl" "..\..\..\bin.v2\libs\function\doc\msvc-8.0\debug\function.docbook"
>>>>>
>>>>> ...failed xslt-xsltproc-dir html\function-doc_HTML.manifest...
>>>>> ...failed updating 1 target..."
>>>>>
>>>>> What does the failure mean ?
>>>> That's weird. Usually programs tell you why things fail. Try running the
>>>> same commands in a shell to see if you get the same problem. Or if it
>>>> gives some useful errors.
>>> Running:
>>>
>>> "xsltproc" --stringparam manifest "function-doc_HTML.manifest"
>>> --xinclude -o "html/" "E:\Programming\Version
>>> Control\Subversion\Boost\tools\boostbook\xsl\html.xsl"
>>> "..\..\..\bin.v2\libs\function\doc\msvc-8.0\debug\function.docbook"
>>>
>>> from the command line succeeds.
>> are you sure? how did you determine that? (i think i've seen exactly
>> this problem already)
>
> By succeed I mean that it returns no errors to stderr or stdout and
> returns no error code of 1 or above.

Has it produced something?
BTW, error code may be less than zero on windows

>>> I have no idea why bjam would say it
>>> fails. What the command is supposed to do I do not know.
>> 1. try "bjam onehtml"
>
> What is that supposed to do ?

 From
http://boost.org/doc/html/boostbook/getting/started.html#boostbook.setup.running:

<quote>
html     HTML output (multiple files). This is the default
onehtml  HTML output in a single HTML file.
</quote>

With metacomm' xsltproc installed, 'bjam html' (or just 'bjam') silently
fails for me, but 'bjam onehtml' works. Binaries from
http://www.zlatkovic.com/libxml.en.html work in both cases.

>> 2. try another xsltproc (e.g. http://www.zlatkovic.com/libxml.en.html)
>
> I will give it a try, but this business of trying to setup and use the
> Boost documentation system, according to instructions, and failing to be
> able to do so, is getting old. I think Boost should either consider
> something better than this mess or get it working someday in this century.
>
> I did get the xsltproc directly from the link in the The BoostBook
> Documentation Format, and that link is at
> http://www.meta-comm.com/engineering/boost/xsltproc-win32.zip. Is that
> link's implementation of xsltproc broken perhaps ?

AFAICT, its purpose is to contain this old fix:
http://mail.gnome.org/archives/xslt/2004-November/msg00030.html

BoostBook docs should be updated to point to binary packages made by
Igor Zlatkovic, IMHO.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[Edward Diener-3]

Ilya Sokolov wrote:

> Edward Diener wrote:
>> Ilya Sokolov wrote:
>>> Edward Diener wrote:
>>>> Rene Rivera wrote:
>>>>> Edward Diener wrote:
>>>>>> ...updating 1 target...
>>>>>> xslt-xsltproc-dir html\function-doc_HTML.manifest
>>>>>>
>>>>>>    set XML_CATALOG_FILES=..\..\..\bin.v2/boostbook_catalog.xml
>>>>>>   "xsltproc" --stringparam manifest "function-doc_HTML.manifest"
>>>>>> --xinclude -o "h
>>>>>> tml/" "E:\Programming\Version
>>>>>> Control\Subversion\Boost\tools\boostbook\xsl\html.
>>>>>> xsl" "..\..\..\bin.v2\libs\function\doc\msvc-8.0\debug\function.docbook"
>>>>>>
>>>>>> ...failed xslt-xsltproc-dir html\function-doc_HTML.manifest...
>>>>>> ...failed updating 1 target..."
>>>>>>
>>>>>> What does the failure mean ?
>>>>> That's weird. Usually programs tell you why things fail. Try running the
>>>>> same commands in a shell to see if you get the same problem. Or if it
>>>>> gives some useful errors.
>>>> Running:
>>>>
>>>> "xsltproc" --stringparam manifest "function-doc_HTML.manifest"
>>>> --xinclude -o "html/" "E:\Programming\Version
>>>> Control\Subversion\Boost\tools\boostbook\xsl\html.xsl"
>>>> "..\..\..\bin.v2\libs\function\doc\msvc-8.0\debug\function.docbook"
>>>>
>>>> from the command line succeeds.
>>> are you sure? how did you determine that? (i think i've seen exactly
>>> this problem already)
>> By succeed I mean that it returns no errors to stderr or stdout and
>> returns no error code of 1 or above.
>
> Has it produced something?

There is no other output to stderr or stdout. It does look as if the
xsltproc command is trying to write output to "html/" but my
understanding is that the -o option is supposed to be a file but the
option in the command line above points to a directory. Is that what is
perhaps causing the problem ? Of course somewhere in the bowels of Boost
Build the xsltproc command line is being generated so I have no idea why
the -o option points to a directory rather than a file. There is nothing
being output in the "html/" relative directory on my machine after
xsltproc is run.

What is most annoying about Boost Build is that one gets back no idea
why something is said to have failed. I find this a real weakness of
Boost Build from the end user's perspective.

> BTW, error code may be less than zero on windows

That may be possible but I have no idea how to check if the errorlevel
is less than zero in a cmd batch file.

>
>>>> I have no idea why bjam would say it
>>>> fails. What the command is supposed to do I do not know.
>>> 1. try "bjam onehtml"
>> What is that supposed to do ?
>
>  From
> http://boost.org/doc/html/boostbook/getting/started.html#boostbook.setup.running:
>
> <quote>
> html     HTML output (multiple files). This is the default
> onehtml  HTML output in a single HTML file.
> </quote>
>
> With metacomm' xsltproc installed, 'bjam html' (or just 'bjam') silently
> fails for me, but 'bjam onehtml' works. Binaries from
> http://www.zlatkovic.com/libxml.en.html work in both cases.

That "onehtml" worked ! Thanks ! However this points out the fact that
something is still broken since without "onehtml" it gives the same
error as before.

>
>>> 2. try another xsltproc (e.g. http://www.zlatkovic.com/libxml.en.html)
>> I will give it a try, but this business of trying to setup and use the
>> Boost documentation system, according to instructions, and failing to be
>> able to do so, is getting old. I think Boost should either consider
>> something better than this mess or get it working someday in this century.
>>
>> I did get the xsltproc directly from the link in the The BoostBook
>> Documentation Format, and that link is at
>> http://www.meta-comm.com/engineering/boost/xsltproc-win32.zip. Is that
>> link's implementation of xsltproc broken perhaps ?
>
> AFAICT, its purpose is to contain this old fix:
> http://mail.gnome.org/archives/xslt/2004-November/msg00030.html

'its' meaning the metacomm link ?

>
> BoostBook docs should be updated to point to binary packages made by
> Igor Zlatkovic, IMHO.

I will try those binaries instead, but if they are better than the
metacomm link, then that metacomm link should have been updated or the
metacomm distribution should have been updated to include fixes in the
other implementation.

It is a real pain when someone like me tries to use the xsltproc in the
documentation, it does not work, and everyone thinks that is par for the
course and not important enough to be fixed, even for the next person
who will run into exactly the same problem. It is understandable only in
that the Boost developers are justifiably far more concerned about
whether their code works rather than whether one can build documentation
from their instructions. The only reason I, as an end user, wanted to
build the code rather than wait for the next release, is because their
were some interesting libraries in the latest Subversion head, whose
documentation I wanted to read, but that documentation must be built.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[Ilya Sokolov]

Edward Diener wrote:

> [snip]

> There is no other output to stderr or stdout. It does look as if the
> xsltproc command is trying to write output to "html/" but my
> understanding is that the -o option is supposed to be a file

You are wrong

> but the
> option in the command line above points to a directory. Is that what is
> perhaps causing the problem ? Of course somewhere in the bowels of Boost
> Build the xsltproc command line is being generated so I have no idea why
> the -o option points to a directory rather than a file. There is nothing
> being output in the "html/" relative directory on my machine after
> xsltproc is run.
>
> What is most annoying about Boost Build is that one gets back no idea
> why something is said to have failed. I find this a real weakness of
> Boost Build from the end user's perspective.

In this case it is not a weakness of Boost Build, it is a bug in
xsltproc (and in your batch file, see below). We are off topic now.

>> BTW, error code may be less than zero on windows
>
> That may be possible but I have no idea how to check if the errorlevel
> is less than zero in a cmd batch file.

if %errorlevel% lss 0 (
   rem errorlevel is less than zero
)
if %errorlevel% neq 0 (
   rem errorlevel is not equal to zero
)
if errorlevel 1 (
   rem warning: errorlevel is equal to or greater than 1
)
if not errorlevel 1 (
   rem warning: errorlevel is less than 1, i.e. 0 or negative!
)

Now I believe that running xsltproc from the command line does not succeeds.

 > [snip]

>>>> 2. try another xsltproc (e.g. http://www.zlatkovic.com/libxml.en.html)
>>> I will give it a try, but this business of trying to setup and use the
>>> Boost documentation system, according to instructions, and failing to be
>>> able to do so, is getting old. I think Boost should either consider
>>> something better than this mess or get it working someday in this century.
>>>
>>> I did get the xsltproc directly from the link in the The BoostBook
>>> Documentation Format, and that link is at
>>> http://www.meta-comm.com/engineering/boost/xsltproc-win32.zip. Is that
>>> link's implementation of xsltproc broken perhaps ?
>> AFAICT, its purpose is to contain this old fix:
>> http://mail.gnome.org/archives/xslt/2004-November/msg00030.html
>
> 'its' meaning the metacomm link ?

Yes

[snip]

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[Edward Diener-3]

Ilya Sokolov wrote:
> Edward Diener wrote:
>
>> [snip]
>
>> There is no other output to stderr or stdout. It does look as if the
>> xsltproc command is trying to write output to "html/" but my
>> understanding is that the -o option is supposed to be a file
>
> You are wrong

Then the documentation for xsltproc is wrong, which is not surprising to me.

>
>> but the
>> option in the command line above points to a directory. Is that what is
>> perhaps causing the problem ? Of course somewhere in the bowels of Boost
>> Build the xsltproc command line is being generated so I have no idea why
>> the -o option points to a directory rather than a file. There is nothing
>> being output in the "html/" relative directory on my machine after
>> xsltproc is run.
>>
>> What is most annoying about Boost Build is that one gets back no idea
>> why something is said to have failed. I find this a real weakness of
>> Boost Build from the end user's perspective.
>
> In this case it is not a weakness of Boost Build, it is a bug in
> xsltproc (and in your batch file, see below). We are off topic now.
>
>>> BTW, error code may be less than zero on windows
>> That may be possible but I have no idea how to check if the errorlevel
>> is less than zero in a cmd batch file.
>
> if %errorlevel% lss 0 (
>    rem errorlevel is less than zero
> )
> if %errorlevel% neq 0 (
>    rem errorlevel is not equal to zero
> )
> if errorlevel 1 (
>    rem warning: errorlevel is equal to or greater than 1
> )
> if not errorlevel 1 (
>    rem warning: errorlevel is less than 1, i.e. 0 or negative!
> )
>
> Now I believe that running xsltproc from the command line does not succeeds.

You are correct. The errorlevel returned is -1073741819.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build