Subject: Re: [Boost-build] Documentation build error on trunk
From: Jurko GospodnetiÄ (jurko.gospodnetic_at_[hidden])
Date: 2012-08-07 02:24:42
>> 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.
> I think this should still use the root project,
> just starting with $(project) instead of
> [ project.current ].
Easily done, but I am not really sure why. What is the special
purpose of using the root project here?
And which 'root project' is that actually ? The one created when
reading the Jamroot file? What about when your build reads in multiple
Jamroot files due to references between separate projects? Should the
'first read Jamroot' project be used then or the one corresponding to
the project requesting this file to be built?
The only difference I can see in which project gets selected for
holding this virtual-target is in what location the actual target file
gets created, and since this is an internally used target, that does not
seem to make much difference. The user can still find it easy enough by
reading the -d2 output or an additional --debug-configuration output
line can be added or something similar.
I guess I'm missing something here...
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