[1.45][signals2] Can't build PDF docs?
I'm trying to build the signals2 docs for the PDF doc distribution, but I'm failing with: warning: failed to load external entity "hello_world_def_code_snippet.xml" tutorial.xml:50: element include: XInclude error : could not load hello_world_def_code_snippet.xml, and no fallback was found warning: failed to load external entity "hello_world_single_code_snippet.xml" tutorial.xml:52: element include: XInclude error : could not load hello_world_single_code_snippet.xml, and no fallback was found warning: failed to load external entity "hello_def_code_snippet.xml" tutorial.xml:63: element include: XInclude error : could not load hello_def_code_snippet.xml, and no fallback was found etc... I can see that process_snippets.exe is being invoked, but I can't find the output xml files anywhere. This occurs if I either build from within the doc/pdf directory, or the libs/signals2/doc directory. Any ideas? Thanks, John.
On Friday 19 November 2010, John Maddock wrote:
I can see that process_snippets.exe is being invoked, but I can't find the output xml files anywhere.
This occurs if I either build from within the doc/pdf directory, or the libs/signals2/doc directory.
Any ideas?
I'm not really competent with Boost.Build. I wrote that Jamfile stuff mostly through a combination of copying other Jamfiles, trial and error, and fumbling around in the dark. It did finally work at least with html though. If anyone more familiar with bjam cares to take a look, the intention was to run snippet_extractor, with the first argument being the output directory for the generated boostbook xml files. The trac ticket https://svn.boost.org/trac/boost/ticket/4872 says the destination dir when running under linux of bin.v2/libs/signals2/doc/gcc-4.4.3/debug is wrong, but thats the directory it uses when I build the html, and it works in that case. What is the proper destination directory for generated documentation xml files?
On Friday 19 November 2010, John Maddock wrote:
I can see that process_snippets.exe is being invoked, but I can't find the output xml files anywhere.
This occurs if I either build from within the doc/pdf directory, or the libs/signals2/doc directory.
Any ideas?
The trac ticket https://svn.boost.org/trac/boost/ticket/4872 says the destination dir when running under linux of bin.v2/libs/signals2/doc/gcc-4.4.3/debug is wrong, but thats the directory it uses when I build the html, and it works in that case. What is the proper destination directory for generated documentation xml files?
That's strange, for me the doc build only succeeds if the xml files are output into the same directory as the Jamfile - they get included by another xml file in that directory yes? John.
On Saturday 20 November 2010, John Maddock wrote:
On Friday 19 November 2010, John Maddock wrote:
I can see that process_snippets.exe is being invoked, but I can't find the output xml files anywhere.
This occurs if I either build from within the doc/pdf directory, or the libs/signals2/doc directory.
Any ideas?
The trac ticket https://svn.boost.org/trac/boost/ticket/4872 says the destination dir when running under linux of bin.v2/libs/signals2/doc/gcc-4.4.3/debug is wrong, but thats the directory it uses when I build the html, and it works in that case. What is the proper destination directory for generated documentation xml files?
That's strange, for me the doc build only succeeds if the xml files are output into the same directory as the Jamfile - they get included by another xml file in that directory yes?
Yes, tutorial.xml for example. However, when bjam runs xsltproc it has a --path option that includes the directory where the generated xml files are (from "bjam -d2" output on trunk in the libs/signals2/doc directory): "xsltproc" --stringparam boost.defaults "Boost" --stringparam boost.root "../../../.." --path "../../../bin.v2/libs/signals2/doc/gcc-4.3.2/debug" --xinclude -o "../../../bin.v2/libs/signals2/doc/gcc-4.3.2/debug/signals.docbook" "/home/fhess/svn/boost_trunk/tools/boostbook/xsl/docbook.xsl" "signals.xml"
OK, after some more testing, it seems that the problem is limited to building with msvc in debug mode - in that case the snippets_extractor executable gets the name of it's pdb file as it's first argument, and the snippets are never generated. The following patch I'm sure isn't the "correct" way to fix this, but it does work for me, HTH, John.
On 21 November 2010 13:20, John Maddock <boost.regex@virgin.net> wrote:
OK, after some more testing, it seems that the problem is limited to building with msvc in debug mode - in that case the snippets_extractor executable gets the name of it's pdb file as it's first argument, and the snippets are never generated.
The following patch I'm sure isn't the "correct" way to fix this, but it does work for me,
Is that the same bug that breaks quickbook testing on windows? Sorry, I never got round to looking into it further. http://lists.boost.org/Archives/boost/2010/06/168277.php Daniel
The following patch I'm sure isn't the "correct" way to fix this, but it does work for me,
Is that the same bug that breaks quickbook testing on windows? Sorry, I never got round to looking into it further.
Frankly I have no idea, sorry! John.
participants (3)
-
Daniel James -
Frank Mori Hess -
John Maddock