Re: [Boost-docs] Quick script for quickbook builds?

Subject: Re: [Boost-docs] Quick script for quickbook builds?
From: Daryle Walker (darylew_at_[hidden])
Date: 2008-08-22 18:18:53


On Aug 21, 2008, at 7:30 PM, Eric Niebler wrote:

> Daryle Walker wrote:
>> On Aug 19, 2008, at 4:54 PM, Eric Niebler wrote:
>> I added another rule to convert that file (trivially) to a *.txt
>> file. But what really want to do is convert that *.qbk.xml file,
>> which is in BoostBook format, into a *.html (or *.pdf) file.
>> There's a Boost.Build/Jam procedure for doing this, but how do I
>> do it manually?
>
> <snip>
>
> I don't think you need a working toolchain. Probably the necessary
> usings in your user-config.jam is enough, and then do:
>
> bjam -a -n -d+2
>
> -a for rebuild all
> -n for don't actually execute the commands
> -d+2 for displaying the commands that would be executed.
>

I think I got an infinite loop somewhere.

1. I added a custom setting for "XML_CATALOG_FILES" to be "$
(BOOST_SVN)/bin.v2/boostbook_catalog.xml"
2. I added some custom rules
   A. Process files matching *.qbk with:
${TARGET_BUILD_DIR}/QuickBook --input-file ${INPUT_FILE_PATH} -I $
{BOOST_SVN} --output-file ${DERIVED_FILES_DIR}/${INPUT_FILE_BASE}.xml
       treating "${DERIVED_FILES_DIR}/${INPUT_FILE_BASE}.xml" as output
   B. Process files matching *.xml with:
/usr/bin/xsltproc --stringparam boost.libraries "${BOOST_SVN}/libs/
libraries.htm" --stringparam boost.root "${BOOST_SVN}" --stringparam
chunk.first.sections "0" --stringparam chunk.section.depth "1" --
stringparam footnote.number.format "1" --stringparam html.stylesheet
"${BOOST_SVN}/doc/html/boostbook.css" --stringparam navig.graphics
"1" --stringparam table.footnote.number.format "1" --stringparam
toc.section.depth "1" --xinclude -o ${DERIVED_FILES_DIR}/$
{INPUT_FILE_BASE}.docbook ${BOOST_SVN}/tools/boostbook/xsl/
docbook.xsl ${INPUT_FILE_PATH}
       treating "{DERIVED_FILES_DIR}/${INPUT_FILE_BASE}.docbook" as
output
   C. Process files matching *.docbook with:
/bin/mkdir -p ${TARGET_BUILD_DIR}/${INPUT_FILE_BASE}_html ; /usr/bin/
xsltproc --stringparam boost.libraries "${BOOST_SVN}/libs/
libraries.htm" --stringparam boost.root "${BOOST_SVN}" --stringparam
chunk.first.sections "0" --stringparam chunk.section.depth "1" --
stringparam footnote.number.format "1" --stringparam html.stylesheet
"${BOOST_SVN}/doc/html/boostbook.css" --stringparam manifest
"standalone_HTML.manifest" --stringparam navig.graphics "1" --
stringparam table.footnote.number.format "1" --stringparam
toc.section.depth "1" --xinclude -o "${TARGET_BUILD_DIR}/$
{INPUT_FILE_BASE}_html/" ${BOOST_SVN}/tools/boostbook/xsl/html.xsl $
{INPUT_FILE_PATH}
       treating "${TARGET_BUILD_DIR}/${INPUT_FILE_BASE}_html/" as
directory output

I'm trying this out with my hat project in the sandbox. I got the
following warning (2 lines) when doing part [B]:

//=============================
warning: failed to load external entity "/Users/daryle/Documents/
Programming/Projects/hat/hat/libs/hat/doc/hat_doxygen.xml"
/Users/daryle/Documents/Programming/Projects/hat/build/hat.build/
Debug/hat.build/DerivedSources/hat.xml:49: element include: XInclude
error : could not load /Users/daryle/Documents/Programming/Projects/
hat/hat/libs/hat/doc/hat_doxygen.xml, and no fallback was found
//=============================

I haven't added any Doxygen-building phases yet. But it seems that
it'll look in the wrong place anyway. (I would put any Doxygen XML
in an intermediate build directory.)

And I think [C] got stuck in an infinite loop, and its processing is
verbose:

//=============================
[I crashed my e-mail client pasting this in; see the (hopefully not
mangled) following attachment instead]


//=============================

(I killed the process after a few minutes.) I'm stumped.

-- 
Daryle Walker
Mac, Internet, and Video Game Junkie
darylew AT hotmail DOT com


This archive was generated by hypermail 2.1.7 : 2017-11-11 08:50:40 UTC