From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-04-05 02:53:11
Douglas Paul Gregor wrote:
> There are some little, pesky issues with the BoostBook tools I'd like to
> resolve at some point, but am a little lost after having been away from
> BBv2 so long:
> 1) catalog.xml: I'm create a file-target with a custom action that creates
> this file. However, I would like to overwrite the file each time. If I
> could just get to the target I would add "ALWAYS $(target) ;" and that
> should do it, but how?
Oops... if you do it, you'll cause the docs to be always generated. Do we
really want it?
The real solution is to update the file if any targets that depend on it are
updated as well. I think a solution already exists in one of the jam
variants. Please see
which talks about IFUSED targets. I don't know how hard it will be to port
this change to bjam.
> 2) html/*.html: Checking out $BOOST_ROOT/doc/html from CVS leaves all of
> the .html files in there read-only, breaking documentation generation. I'd
> like to either mark these files writable or just delete them all.
Could you just add "rm -rf" to the xslt-xsltproc-dir action? Of course, the
really right solution would be to add a new rule to 'common.jam' that will
return the exact command for recursive removal used on a specific platform.
This solution is not without problems. For example, I often copy boostbook.css
to the html directory by hand. Any solution which does not know the names of
all files to remove will also remove that file.
> 3) Does anyone remember why we commented out the "using boostbook ;" in
(1) This used to cause hard error if BOOST_ROOT is not defined
(2) The idea is that user-config.jam should contain no uncommented code,
just because the user decides what to enable and what not. Of course, "using
boostbook ; " can be placed to Boost's project-root.jam
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk