[Boost-build] Documentation toolchain, ease of use

Subject: [Boost-build] Documentation toolchain, ease of use
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2011-02-04 11:50:57

AMDG

For tools that only support a single configuration,
when default initialization is good enough, it
would be nice if the configuration files didn't
need to be adjusted.  (Just like a default
compiler is selected if none is configured).

So, here's what I propose to do:

a) Change all documentation Jamfiles to have
    using quickbook ;
    using boostbook ;
    using doxygen ;
    (or whatever's appropriate)
b) boostbook should lazily initialize the
    tools it depends on (xsltproc and fop).
    doxygen should lazily initialize boostbook.
c) Attempting to default initialize any of
    these tools after they've already been
    initialized should be a no-op.  (I think
    this is already true, but I need to check
    again.)
d) Deprecate the *-config modules and move
    their functionality into the main module.
    (This should be mostly done already).

Thoughts?

In Christ,
Steven Watanabe