From: Dave Rahardja (drahardja_at_[hidden])
Date: 2007-04-02 08:44:55
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
lib b : b.cpp bb.cpp
lib b-includes : null.cpp
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?
> -----Original Message-----
> From: boost-build-bounces_at_[hidden]
> [mailto:boost-build-bounces_at_[hidden]] On Behalf Of
> Vladimir Prus
> Sent: Monday, April 02, 2007 2:19 AM
> To: boost-build_at_[hidden]
> Subject: Re: [Boost-build] Passing include directories
> between libraries
> On Saturday 31 March 2007 20:06, Dave Rahardja wrote:
> > Hi group.
> > Let's say I have two libraries, a.lib and b.lib, each with
> its own Jamfile,
> > under a common Jamroot.
> > I need a.lib to know about the header directory of b.lib,
> and vice versa.
> > How do I do this?
> I don't know what you mean by "know about the header
> directory". If you
> want a.lib to be compiled with include path to b.lib, then I'd use:
> lib a : .... : <include>../b/whatever ;
> Normally, I recommend usage requirements:
> lib b
> : # sources
> : # requirements
> : # default build
> : <include>whatever ;
> lib a : b <some other sources> ;
> However you say that a should use b's includes and b should
> use a's includes. Such circular dependency between Boost.Build targets
> is not allowed, therefore you'd have to use <include>whatever for
> your a and b targets.
> - Volodya
> Unsubscribe & other changes:
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