From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-03-19 05:31:30
> > OK, since I don't have any use for xml-catalog, I've no problem if this
> > is implementation detail. But I'm not sure what "Jam variables" mean. The
> > general V2 approach is to avoid variables as much as possible. For
> > example, to configure gcc, you might say
> > using gcc : 3.2 g++-3.2 ;
> > instead of setting any variables directly. Probable this wouls be good
> > for BookBook as well.
> Very nifty. I've now done the same for BoostBook, where one can configure
> the DocBook XSL and DTD directories as such:
> using boostbook : /home/gregod/Projects/share/docbook-xsl-1.60.1/
> : /home/gregod/Projects/share/docbook-dtd-4.2/
I like it very much!
> I have one serious concern with the XML catalog generation I just checked
> in: the command lines to "echo" can get pretty darn long, but I don't
> really know how to break them up properly. Or perhaps there is a better way
> to generate files than echo?
When generating response file we use 'piecemeal' action. But I can't see how
it can be used here. Probably, you can look at facilities in 'print.jam': the
'output' rule and 'text' rule. They seem to run 'echo' line-by-line.
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