John Maddock wrote:
Steven Watanabe wrote:
AMDG
John Maddock wrote:
Some rather basic documentation for the tool itself is here: http://svn.boost.org/svn/boost/sandbox/tools/auto_index/doc/html/index.html note that currently there is no Boost.Build integration - I really need some help with that - so the tool is much harder to use than it should be.
I've worked out how to insert an extra tool in the middle of the boostbook toolchain. See attached.
Thanks for making this!
That would be way cool, but it doesn't work for me:
I cut and pasted your code into the type_traits Jamfile.v2,
...
What am I doing wrong?
Pasting the code :-) Please save Steven's attachment into a file, tools/build/v2/tools/modified-docbook.jam and add import modified-docbook ; in your jamfile. You need to this it this way because the names of actions are qualified by the module name, or if you put this code into a different file, you need to change this code.
And with "<modify-docbook>on" I see:
c:/data/boost/boost/trunk/tools/build/v2/kernel\modules.jam:103: in modules.call-in rule modified-docbook.modify-docbook unknown in module modified-docbook.
This should be gone if you save into right file.
and without "<modify-docbook>on" I see: > c:/data/boost/boost/trunk/tools/build/v2/tools\boostbook.jam:359: in object(boostbook-generator)@73.run warning: rulename $(base-target).depends expands to empty string
Please try the attached revision. Steven, your original code did nothing when modify-docbook=off -- however, Boost.Build first processes generator overrides, and then runs generator. The standard docbook generator gets overriden, and if your custom generator returns nothing, no attempt to use the standard generator is made. The attached version explicitly tries to construct DOCBOOK again. Another alternative is to add '<modify-docbook>on' to generator requirements, so it's not even considered if not needed. Thanks, Volodya