Boost logo

Boost-Build :

Subject: Re: [Boost-build] BUMPITTY BUMP: [git] genrating forward headers
From: Vladimir Prus (ghost_at_[hidden])
Date: 2013-09-12 11:07:34

On 27.08.2013 23:43, Bjørn Roald wrote:

> I added a new project at libs/Jamfile.v2 to add <implicit-dependency>/boost//headers to all library and test targets. Likewise I added
> similar requirements to project level in tools/Jamfile.v2 and various Jamroot files I could find. See:
> As use of <implicit-dependency>/boost//headers after substitution shall cause any new any effect in SVN layout, I removed the guards I had
> in earlier patches at project level. This make things simpler, but it may have side effects we don't want.


quick question - if we have implicit dependency on headers in libs/Jamfile.v2, do we still need such references in Jamfiles for individual
libraries, or those can be eliminated.

> known issues in modularized layout:
> ===================================
> b2 modularized layout issue 1:
> ------------------------------
> build in status require build in root first, at a minimum
> b2 headers
> but default targets with just b2 seems to work as well. I think all remaining header links not used by any of the library builds get
> created at the end. Maybe stage target depends on headers target or something, I have not checked. Logically that would make sense.

Which targets on 'status' fail to build headers? I think adding implicit dependency to status/Jamfile.v2 shall work.

> b2 modularized layout issue 2:
> ------------------------------
> install require header links to proxy the SVN layout. The install glob needs update to get the headers from the sources according to
> Steven. I have no idea how to do that.

Could you clarify this requirement?


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