Boost logo

Boost-Build :

Subject: Re: [Boost-build] feature, properties, variants, and all the rest
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2017-07-29 18:13:09


On 07/29/2017 11:48 AM, Stefan Seefeld via Boost-build wrote:
> OK. I suppose instead of the explicit "<include>/a/path" I could also
> write an action (used to build A) that determines "/a/path", yes ? How
> would I push that onto the usage requirements of A ?

  You should probably consider a custom target type.
The ac module has code that does something like this.
(It's a bit more complex, because it also finds a
library in addition to the header and caches the
compile checks.)
The important part is ac-library.construct (line 172)
which returns the usage requirements.

Note lines 234 and 251
 return [ $(library[1]).add-raw <include>$(includes) ] $(library[2-]) ;
which adds the include path to the usage requirements.

In Christ,
Steven Watanabe

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at