From b5b5f90a795ea2bdb923b6fe1dddc846afe4f63e Mon Sep 17 00:00:00 2001 From: Adrian Bunk Date: Mon, 15 Jul 2019 11:44:10 +0300 Subject: ref-manual: Remove documentation for the removed bluez5 distro feature bluez4 was removed even from meta-oe 2 years ago, which made made the bluez5 feature for selecting between bluez4 and bluez5 mandatory for using the bluetooth feature. The backfilled bluez5 feature has been removed, including the bluetooth class that helped recipes for selecting between bluez4/bluez5. Recipes can replace ${BLUEZ} with bluez5. (From yocto-docs rev: 025e2b5797b987b0260d7410e2e6d7283f5a7e91) Signed-off-by: Adrian Bunk Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-classes.xml | 17 ----------------- documentation/ref-manual/ref-features.xml | 21 --------------------- 2 files changed, 38 deletions(-) (limited to 'documentation') diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml index ece47e757b..37619e382d 100644 --- a/documentation/ref-manual/ref-classes.xml +++ b/documentation/ref-manual/ref-classes.xml @@ -318,23 +318,6 @@ -
- <filename>bluetooth.bbclass</filename> - - - The bluetooth class defines a variable that - expands to the recipe (package) providing core - bluetooth support on the platform. - - - - For details on how the class works, see the - meta/classes/bluetooth.bbclass file in the Yocto - Project - Source Directory. - -
-
<filename>buildhistory.bbclass</filename> diff --git a/documentation/ref-manual/ref-features.xml b/documentation/ref-manual/ref-features.xml index b057d2d040..44ba67cf50 100644 --- a/documentation/ref-manual/ref-features.xml +++ b/documentation/ref-manual/ref-features.xml @@ -154,27 +154,6 @@ bluetooth: Include bluetooth support (integrated BT only). - bluez5: Include - BlueZ Version 5, which provides core Bluetooth layers and - 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: -- cgit v1.2.3-54-g00ecf