Re: [jamboost] BoostBook and Boost.Build version 2

From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-03-17 01:44:24

Douglas Gregor wrote:
> On Friday 14 March 2003 09:02 am, Douglas Gregor wrote:
> > > What's your plan of action now? I'd suggest that "XML + XSL -> XML"
> > > transformation should be implemented first, followed by "XML + XSL ->
> > > dir + manifest file". This will allow to do complete generation
> > > sequence for one format. The 'docbook' rule on top of that (with
> > > feature to select format). Lastly, dependency scanning.
> >
> > I'm going to take a crack at it now. Expect a flood of silly questions
> > soon
> >
> > :)
> >
> > Doug
>
> My 2nd pass at it is now in CVS (tools/build/new/boostbook.jam). The
> generators seem to be generating happily, and it was actually quite trivial
> to get an XInclude scanner working for XML documents. Kudos to the BBv2
> developers for a _very_ extensible build system.

Thanks!
But frankly, I was quite surprised this morning while browsing commit emails. 
First I see rather complete implementation of transformation, and twenty 
minutes later scanner follows. You've quick!

> I'm fighting a little bit with the documentation system living in a
> compiler's world. My documents end up in "bin/gcc/debug/", whereas the
> current directory would be more appropriate. I know I could just override
> the target path, but I'm wondering if there's some better way to say "these
> features don't apply to me".

Not yet. I have the same problem with parser generator, and a literate 
programming tool. It will be addressed in future, but this seems tolerable 
for a while to me.

- Volodya