From: Anthony Novatsis (anthonynovatsis_at_[hidden])
Date: 2007-04-02 09:23:28
You can do this with an alias:
alias header_only_library : : : : <include>/usr/include/header_only_library ;
In your example:
alias a-includes : : : : <include>a/headers ;
And then specify a-includes for lib b in the same as you have already done:
lib b : b.cpp bb.cpp a-includes : : : ;
> Message: 10
> Date: Mon, 2 Apr 2007 07:44:55 -0500
> From: "Dave Rahardja" <drahardja_at_[hidden]>
> Subject: Re: [Boost-build] Passing include directories between
> To: "'Boost.Build developer's and user's list'"
> Message-ID: <017c01c77524$b8fab8e0$fa01a8c0_at_TALON>
> Content-Type: text/plain; charset="us-ascii"
> Yes, that's what I mean. However, I want lib a to "know" about its
> directories, and lib b to "know" about _its_ directories. In other words, I
> want to maintain use usage-requirements.
> I've been able to do it this way so far:
> --- a/Jamfile ---
> lib a : a.cpp aa.cpp
> lib a-includes : null.cpp
> : <include>a/headers
> --- b/Jamfile
> lib b : b.cpp bb.cpp
> lib b-includes : null.cpp
> : <include>b/headers
> So you see, I had to build a "dummy" library with an empty null.cpp file, in
> order to export _only_ the usage-requirements <include> to the users of the
> Is there a better way to do this?
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