From: Greg Landrum (greg.landrum_at_[hidden])
Date: 2008-04-07 23:58:27
Thanks for the response Volodya.
I've got a short follow-up question below just to make sure I understand.
On Mon, Apr 7, 2008 at 9:26 AM, Vladimir Prus <ghost_at_[hidden]> wrote:
> What you observe is a known limitation. When you build from root, the
> targets in a/Jamfile are built, including this:
> alias children : a1 a2 ;
> This cause a/a1/Jamfile to be read, and it defines the /BoostBuildSample/a/a1
> project id. So, when we get to build a2, that project id is known, and things work.
> However, when you build in /BoostBuildSample/a/a2, the 'alias children' is not
> build, and nothing causes a/a1/Jamfile to be read.
> You can workaround this by adding:
> use-project BoostBuildSample/a/a1 : a1 ;
> to a/Jamfile
Ok, this works. It looks like I also need to include :
use-project BoostBuildSample/a : a ;
use-project BoostBuildSample/b : b ;
in my Jamroot to be able to reference the a/ subprojects from the b
directories and vice versa.
The revised tarball is here:
> There is an issue in the tracker to make project IDs more flexible.
In the meantime, is there a suggested pattern for handling this, or
does the approach I'm using (a hierarchy with all the use-project's)
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