Re: [Boost-build] Inserting an extra stage into the BoostBook toolchain?

Subject: Re: [Boost-build] Inserting an extra stage into the BoostBook toolchain?
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2008-11-15 12:02:12

Alexander Sack wrote:

> On Sat, Nov 15, 2008 at 7:35 AM, John Maddock <john_at_[hidden]> wrote:
>> OK, I have a very primitive automatic indexer, that accepts Docbook XML as
>> input along with a concordance/script file and outputs another Docbook XML
>> file with index entries inserted.  It would speed up development a great
>> deal if I could insert this tool into the regular quickbook/boostbook build
>> process, anyone have any pointers on how to achieve this?  And yes, I've
>> looked at the extender manual, but can't see at present how to modify an
>> existing tool chain...
> 
> John, I'm not familiar with Docbook but from your description above I
> see that you have some tool that takes XML and script input and pops
> out another XML file.  Is there any reason why you don't use a notfile
> or make rule to do the dirty work?  Generators are typically used to
> to allow Boost.Build to manage generated source codes files which
> isn't really the case here.  You can write a custom generator that
> handles non-source related files (there are several examples in
> $BOOST_BUILD_PATH/tools/*.jam) but this is way more involved.
> 
> Again, have you seen this part of the doc?
> 
> http://www.boost.org/doc/tools/build/doc/html/bbv2/builtins/raw.html
> 
> You could write a custom rule that would just to the dirty work for you...

This is probably not very attactive. We want 

        boostbook a : a.xml ;

to work. John, where exactly this new tool should be inserted, and should it
always be run, or under some conditions?

- Volodya