David A. Greene wrote:
This has been going on for six months now and is preventing me from opening up NTP for comments so that I may eventually submit it. I'm at a total loss for what to try next.
I'm attaching a gzipped file that contains just the bare minimum to get
things running *outside* the boost tree. I built this example on top of
the example you posted here earlier. This works better with the patches
I posted under "[boostbook] stylesheet issues" but they aren't required
to test the configuration.
To try it out,
1. unpack the archive somewhere, everything is packed inside a
single directory.
2. define the environment variable BOOST_BUILD_PATH to point to the
root of your boost installation.
3. cd into boost-doc-sample/libs/ntp/doc/
4. invoke bjam
For example, under sh
> tar -xzvf boost-doc-sample.zip
> export BOOST_BUILD_PATH=/path/to/boost
> cd boost-doc-sample/libs/ntp/doc/
> bjam --v2
If it works you can try moving your actual setup into this tree and see
how it goes.
If this still fails, can you send me the output of "bjam --v2 -a" (-a
for rebuild all) in the same directory.
You may also want to try "bjam --v2 -a -n" for a dry-run, and try
running the command lines manually to figure out what's going on.
I'm assuming you'll have a recent CVS checkout of Boost (v1.33 should
also be fine), bjam, xsltproc and doxygen installed (try running those
from the command line just to be sure) and a compiler toolset configured
in either user-config.jam or site-config.jam (needed to compile quickbook).
For bonus points you should also have a local copy of DocBook xml and
xsl and boostbook properly configured to use those in either
user-config.jam or site-config.jam.
Awaiting the results... ;-)
João
boost-doc-sample.tar.gz
Description: GNU Zip compressed data
