diff options
author | Patrick Ohly <patrick.ohly@intel.com> | 2017-06-09 15:04:03 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-06-12 15:04:12 +0100 |
commit | 3b3ae91a22d6f685e804df4f32cdeebe1bd6bd88 (patch) | |
tree | cfabf9d8949350bab93854423994a2c9dc866e61 /README | |
parent | 9c91df324dfe58273f5a1d1d33dba1d34a180db7 (diff) | |
download | openembedded-core-3b3ae91a22d6f685e804df4f32cdeebe1bd6bd88.tar.gz openembedded-core-3b3ae91a22d6f685e804df4f32cdeebe1bd6bd88.tar.bz2 openembedded-core-3b3ae91a22d6f685e804df4f32cdeebe1bd6bd88.zip |
bitbake.conf: DISTRO_FEATURES as overrides
As discussed in "[Openembedded-architecture] Yocto Compatible 2.0 +
signature changes", changes in .bbappend must depend on some explicit
configuration change, typically selecting a distro feature.
For _append and _remove, adding an override that is set only when the
corresponding entry is in DISTRO_FEATURES achieves that:
In local.conf:
DISTRO_FEATURES_append = " my-distro-feature"
In layer.conf:
DISTRO_FEATURES_OVERRIDES += "my-distro-feature"
In a .bbappend:
do_install_append_df-my-distro-feature () {
...
}
The subset of DISTRO_FEATURES that are made available as overrides
must be configured explicitly because using them this way should
be a conscious decision.
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions