Subject: [Boost-build] features with 'propagate' attribute
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2017-03-30 17:58:47
how is the 'propagate' feature attribute handled. If I were to guess, I
would assume that all 'propagate' features of a target are merged into
all dependent targets feature sets. Is that right ?
So, a target's feature set is composed of:
* default features
* features provided on the command line
* features explicitly added to target definitions
* features propagated from 'source' targets
* features from 'usage requirements' from 'source' targets
Is that correct ? What are the merge rules in this, i.e. in what order
may features from the above sources take precedence in the accumulated
feature set ?
-- ...ich hab' noch einen Koffer in Berlin...
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