Re: [boost] [EXTERNAL] [testing] mpl/core tests not visible

Subject: Re: [boost] [EXTERNAL] [testing] mpl/core tests not visible
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2014-09-13 18:06:56

On Saturday 13 September 2014 21:25:58 Belcourt, Kenneth wrote:
> On Sep 13, 2014, at 3:11 PM, Andrey Semashev <andrey.semashev_at_[hidden]> 
wrote:
> > 
> > I suppose, the expectation is that b2 will infer the dependent headers
> > from
> > the compiled sources somehow and installs them. It's possible that it is
> > not able to pass through the preprocessor magic used in MPL. I think
> > there was a discussion some time ago about some headers not being
> > automatically installed this way. Although that doesn't explain why only
> > some testers were broken.
>
> It’s because I don’t remove the existing boost directory so it’s already
> fully (correctly) populated.  These testers will also fail if I remove
> their boost directories.
>
> > Anyway, IMHO, 'b2 headers' should be explicitly invoked by the testing
> > scripts.
> 
> Right, testers would be okay with that though I think a breaking change like
> this needs a bit more visibility so that testers, developers, and others,
> understand this change.

It is possible that this never worked before, not in complicated cases like 
MPL anyway. At some point someone ran 'b2 headers' or something similar on the 
test machine, and it worked while the headers layout in submodules was more or 
less stable.