ping
On Mon, Jul 15, 2019 at 11:44:10AM +0300, Adrian Bunk wrote:
> 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.
>
> Signed-off-by: Adrian Bunk <b...@stusta.de>
> ---
> documentation/ref-manual/ref-classes.xml | 17 -----------------
> documentation/ref-manual/ref-features.xml | 21 ---------------------
> 2 files changed, 38 deletions(-)
>
> 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 @@
> </para>
> </section>
>
> -<section id='ref-classes-bluetooth'>
> - <title><filename>bluetooth.bbclass</filename></title>
> -
> - <para>
> - The <filename>bluetooth</filename> class defines a variable that
> - expands to the recipe (package) providing core
> - bluetooth support on the platform.
> - </para>
> -
> - <para>
> - For details on how the class works, see the
> - <filename>meta/classes/bluetooth.bbclass</filename> file in the Yocto
> - Project
> - <link linkend='source-directory'>Source Directory</link>.
> - </para>
> -</section>
> -
> <section id='ref-classes-buildhistory'>
> <title><filename>buildhistory.bbclass</filename></title>
>
> 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 @@
> </para></listitem>
> <listitem><para><emphasis>bluetooth:</emphasis> Include
> bluetooth support (integrated BT only).</para></listitem>
> - <listitem><para><emphasis>bluez5:</emphasis> Include
> - BlueZ Version 5, which provides core Bluetooth layers and
> - protocols support.
> - <note>
> - The default value for the
> - <filename>DISTRO FEATURES</filename> 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
> - <link
> linkend='var-DISTRO_FEATURES_BACKFILL_CONSIDERED'><filename>DISTRO_FEATURES_BACKFILL_CONSIDERED</filename></link>
> - variable as follows:
> - <literallayout class='monospaced'>
> - DISTRO_FEATURES_BACKFILL_CONSIDERED = "bluez5"
> - </literallayout>
> - 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.
> - </note>
> - </para></listitem>
> <listitem><para><emphasis>cramfs:</emphasis> Include CramFS
> support.</para></listitem>
> <listitem><para><emphasis>directfb:</emphasis>
> --
> 2.17.1
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
