I'm looking into building PDF versions of the docs for 1.40 and I'm having trouble building the signals2 docs. For example if I cd into libs/signals2/doc and build from there, then the XML code snippets aren't found. Likewise if I build as a dependency from doc/pdf. Any ideas? Thanks, John.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 21 August 2009, John Maddock wrote:
It works for me. I don't think I've ever tried to build pdf output though, only html. What error messages do you get? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqO7UgACgkQ5vihyNWuA4VrLgCcCM7F3tc2oh534JGjFmWdqzkp SgQAoKlBoNTaOniruMbde56tvox2fCJ4 =l9JB -----END PGP SIGNATURE-----
For now, I'm just trying to build the HTML from within libs/signals2/doc, it builds cleanly with apparently no errors, but there were some "failed to load external entity" XSLT warnings that lead to the HTML having no code snippets in it, for example the first section of the tutorial contains: "Hello, World! (Beginner) The following example writes "Hello, World!" using signals and slots. First, we create a signal sig, a signal that takes no arguments and has a void return value. Next, we connect the hello function object to the signal using the connect method. Finally, use the signal sig like a function to call the slots, which in turns invokes HelloWorld::operator() to print "Hello, World!". <xi:include></xi:include> <xi:include></xi:include>" Which is clearly not intended. The program that extracts the code snippets seems to run OK, I just don't see any generated XML files anywhere? This is on Windows BTW. Thanks, John.
On Saturday 22 August 2009, John Maddock wrote:
When I build on linux, the snippets get put in bin.v2/libs/signals2/doc/gcc-4.3.2/debug/ and "bjam -d2" shows it running xsltproc with a --path "../../../bin.v2/libs/signals2/doc/gcc-4.3.2/debug" option: xslt-xsltproc ../../../bin.v2/libs/signals2/doc/gcc-4.3.2/debug/signals.docbook XML_CATALOG_FILES=../../../bin.v2/boostbook_catalog.xml export XML_CATALOG_FILES "xsltproc" --stringparam boost.libraries "../../../libraries.htm" --stringparam boost.root "../../../.." --stringparam html.stylesheet "../../../../doc/html/boostbook.css" --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"
There's something compiler dependent going on here: * The --path option passed to xsltproc appears to be correct whatever compiler I use, but: * Building with msvc-8 results in no XML files generated - leading to xsltproc errors * Building with gcc-3 (Mingw32) results in XML files that are all empty - leading to more xsltproc errors * Building with gcc-4 (Mingw32 alpha) results in valid xml files. Any ideas? Cheers, John.
On Saturday 22 August 2009, John Maddock wrote:
Try applying changeset [55722] in trunk: https://svn.boost.org/trac/boost/changeset/55722/trunk/libs/signals2/doc/sni... it fixes the problem with mingw gcc3 for me at least. Apparently, some compilers set an error bit when you call the close method of a default constructed ofstream, and some don't.
Thanks, that fixes things for gcc-3 (tested cygwin and mingw32), but msvc and Intel-win still produces no xml files :-( John.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 23 August 2009, John Maddock wrote:
Unfortunately, I don't have msvc8 or intel-win compilers. I could download msvc9 express, but IIRC I did that at some time in the past and the little snippet_extractor.cpp program worked. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqSmCIACgkQ5vihyNWuA4WwrgCeMDHxdxSB84wuM1vk9qC0Fo7n 5/MAoI360oyqb+rXG0laNaxU4+GvGGdq =10mb -----END PGP SIGNATURE-----
participants (3)
-
Frank Mori Hess -
Frank Mori Hess -
John Maddock