Subject: Re: [boost] [build] [config] check_target_builds and feature.subfeature composition
From: Edward Diener (eldiener_at_[hidden])
Date: 2017-05-30 00:19:09
On 1/23/2017 8:41 PM, Steven Watanabe wrote:
> On 01/23/2017 05:17 PM, Peter Dimov wrote:
>> Edward Diener wrote:
>>> Has no one else encountered the same problems I have encountered using
>>> the feature.subfeature facility in Boost Build?
>> Yes I have, I brought it up, nothing happened. I stopped using
> The problem is that check_target_builds tries to
> guess which features are important, and does it
> badly (via a hard-coded list).
I would have thought that it was the feature.subfeature not
distinguishing correctly between different builds, based on
subfeaturees, that was the culprit.
It is hardly possible for me not to use check_target_builds, since it is
an integral part of predefs and also an integral part of the build time
configuration of config; and I find both of these eminently useful. So
my solution is to not use feature.subfeature and instead encode
so-called subfeatures in the version field of a toolset. Since builds
are automatically distinguished by the toolset-version encoding this
always works properly for me.
> In Christ,
> Steven Watanabe
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk