Subject: Re: [Boost-build] Global headers across projects
From: Phillip Seaver (phil_at_[hidden])
Date: 2008-10-15 11:19:47
Alexander Sack wrote:
> On Tue, Oct 14, 2008 at 3:38 PM, Steven Watanabe <watanabesj_at_[hidden]> wrote:
>> Alexander Sack wrote:
>>> alias common_headers : : : <include>h1_dir <include>h2_dir>;
>>> However I can't use this in my Jamroot's project definition as a
>>> requirement a la:
>>> project myproj
>>> : requirements common_headers
>> project myproj : requirements <source>common_headers ;
>>> constant some_headers : <include>blah blah etc.
> Still does not work - I tried this btw:
> error: Unable to find file or target named
> error: 'common_headers'
> error: referred from project at
> error: <somepath>
> So my project hierarchy looks like this:
> I'm calling bjam against myproj/liba/Jamfile which calls build-project
> subcomponentA ; etc.
> I'm assuming that all sub projects in my hierarchy inherit
> requirements from Jamroot right?
That's the way it's working for me. I have "project apago :
requirements <variant>debug:<define>_DEBUG ...". You might try putting
the includes directly on the project instead of using an alias. Like this:
project myproj : requirements <include>h1_dir <include>h2_dir ;
Also, I just noticed that in an earlier email, you have
"<include>h2_dir>;" If that's what you actually have in your Jamroot,
that would cause a problem, since it would add "h2_dir>;" as an include
path and would not terminate the alias target, since there has to be a
space before the semi-colon (";"). If that's what you have, you should
try changing that first.
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