From: Reece Dunn (msclrhd_at_[hidden])
Date: 2004-04-05 13:14:16
Vladimir Prus wrote:
>Douglas Paul Gregor wrote:
> > 2) html/*.html: Checking out $BOOST_ROOT/doc/html from CVS leaves all of
> > the .html files in there read-only, breaking documentation generation.
> > 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
>to the html directory by hand. Any solution which does not know the names
>all files to remove will also remove that file.
I am currently using the following script file:
rm -f -r html
rm -f ../c++boost.gif
##### build the documentation
bjam -a --v2
##### publish the files
for im in $root/doc/html/images/*.png ; do
cp $im --target-directory=html/images
cp $root/doc/html/boostbook.css html/boostbook.css
cp $root/c++boost.gif ../c++boost.gif
rm -r bin
This then allows me to build the docs automatically and have the right image
files and CSS file in the correct places.
Sign-up for a FREE BT Broadband connection today!
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