Subject: Re: [Boost-build] Documentation build error on trunk
From: Jurko GospodnetiÄ (jurko.gospodnetic_at_[hidden])
Date: 2012-08-06 10:55:23
> I'll look into it now and let you know how it goes...
I think I've resolved the issue in revision .
Daniel, could you test on your end and see if this resolves your
issues? Hopefully without introducing any new ones. :-)
I'll commit a few more cleanup patches I have lined up, but this
should be a minimal fix for the problem at hand.
The issue was that the boostbook toolset wants to generate some sort
of a global xml catalog file (whatever that is :-)) needed when
generating its boostbook targets. This catalog file does not seem to
change between different invocations and so the toolset wants to reuse
it instead of generating a new one for every boostbook
target/property-set/project. To achieve this it created the the
xml-catalog's virtual-target and had it registered to the 'root boost
build project'. To reach this 'root project' it used a dirty trick
relying on Boost Build leaving its 'currently loaded project' reference
dangling even after done with loading all of its project modules. Now I
changed it to not use the root project at all but to simply use the
first project requesting this file instead.
Ideally this target would get registered to the central 'boostbook'
project but that is a standalone project without a 'location folder',
i.e. it can not create new targets but only reference preexisting ones.
This is something that can be changed if Boost Build is updated to allow
creating new targets from stand-alone projects, but the current solution
seems clean enough for me.
Hope this helps.
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