summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorAdrian Bunk <bunk@stusta.de>2019-07-15 11:44:10 +0300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2019-09-10 11:21:55 +0100
commitb5b5f90a795ea2bdb923b6fe1dddc846afe4f63e (patch)
treee2fab3dfbec542cb110d8827e6af502706789959 /documentation
parentd7441ddb0c49eafdb620dc45fb7e9a2a92790767 (diff)
downloadpoky-b5b5f90a795ea2bdb923b6fe1dddc846afe4f63e.tar.gz
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 <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/ref-manual/ref-classes.xml17
-rw-r--r--documentation/ref-manual/ref-features.xml21
2 files changed, 0 insertions, 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 @@
318 </para> 318 </para>
319</section> 319</section>
320 320
321<section id='ref-classes-bluetooth'>
322 <title><filename>bluetooth.bbclass</filename></title>
323
324 <para>
325 The <filename>bluetooth</filename> class defines a variable that
326 expands to the recipe (package) providing core
327 bluetooth support on the platform.
328 </para>
329
330 <para>
331 For details on how the class works, see the
332 <filename>meta/classes/bluetooth.bbclass</filename> file in the Yocto
333 Project
334 <link linkend='source-directory'>Source Directory</link>.
335 </para>
336</section>
337
338<section id='ref-classes-buildhistory'> 321<section id='ref-classes-buildhistory'>
339 <title><filename>buildhistory.bbclass</filename></title> 322 <title><filename>buildhistory.bbclass</filename></title>
340 323
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 @@
154 </para></listitem> 154 </para></listitem>
155 <listitem><para><emphasis>bluetooth:</emphasis> Include 155 <listitem><para><emphasis>bluetooth:</emphasis> Include
156 bluetooth support (integrated BT only).</para></listitem> 156 bluetooth support (integrated BT only).</para></listitem>
157 <listitem><para><emphasis>bluez5:</emphasis> Include
158 BlueZ Version 5, which provides core Bluetooth layers and
159 protocols support.
160 <note>
161 The default value for the
162 <filename>DISTRO FEATURES</filename> variable includes
163 "bluetooth", which causes bluez5 to be backfilled in
164 for bluetooth support.
165 If you do not want bluez5 backfilled and would rather
166 use bluez4, you need to use the
167 <link linkend='var-DISTRO_FEATURES_BACKFILL_CONSIDERED'><filename>DISTRO_FEATURES_BACKFILL_CONSIDERED</filename></link>
168 variable as follows:
169 <literallayout class='monospaced'>
170 DISTRO_FEATURES_BACKFILL_CONSIDERED = "bluez5"
171 </literallayout>
172 Setting this variable tells the OpenEmbedded build
173 system that you have considered but ruled
174 out using the bluez5 feature and that bluez4 will be
175 used.
176 </note>
177 </para></listitem>
178 <listitem><para><emphasis>cramfs:</emphasis> Include CramFS 157 <listitem><para><emphasis>cramfs:</emphasis> Include CramFS
179 support.</para></listitem> 158 support.</para></listitem>
180 <listitem><para><emphasis>directfb:</emphasis> 159 <listitem><para><emphasis>directfb:</emphasis>