From: Scott Rifenbark Date: Tue, 21 Jun 2016 21:26:58 +0000 (-0700) Subject: ref-manual: Updated the DISTRO_FEATURES description of Bluez5 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=fc518b5a48d0b4036183e345ae1ee11574e07be7;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git ref-manual: Updated the DISTRO_FEATURES description of Bluez5 Edits to explain that by default, DISTRO_FEATURES backfills bluetooth support with Bluez5. If the user wants to use the Bluez4 feature, they need to backfill consider Bluez5. (From yocto-docs rev: 4e8b34c8c5841cdc1cae564decae4689ae4f2b11) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- diff --git a/documentation/ref-manual/ref-features.xml b/documentation/ref-manual/ref-features.xml index 267dea9568e..cd1bcb0243b 100644 --- a/documentation/ref-manual/ref-features.xml +++ b/documentation/ref-manual/ref-features.xml @@ -146,7 +146,25 @@ bluetooth support (integrated BT only). bluez5: Include BlueZ Version 5, which provides core Bluetooth layers and - protocols support. + protocols support. + + The default value for the + DISTRO FEATURES + variable includes "bluetooth", which causes bluez5 + to be backfilled in for bluetooth support. + If you do not want bluez5 backfilled and would rather + use bluez4, you need to use the + DISTRO_FEATURES_BACKFILL_CONSIDERED + variable as follows: + + DISTRO_FEATURES_BACKFILL_CONSIDERED = "bluez5" + + Setting this variable tells the OpenEmbedded build + system that you have considered but ruled + out using the bluez5 feature and that bluez4 will be + used. + + cramfs: Include CramFS support. directfb: