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 <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
45baa90c8c
commit
fc518b5a48
|
@ -146,7 +146,25 @@
|
|||
bluetooth support (integrated BT only).</para></listitem>
|
||||
<listitem><para><emphasis>bluez5:</emphasis> Include
|
||||
BlueZ Version 5, which provides core Bluetooth layers and
|
||||
protocols support.</para></listitem>
|
||||
protocols support.
|
||||
<note>
|
||||
The default value for the
|
||||
<link linkend='var-DISTRO_FEATURES'><filename>DISTRO FEATURES</filename></link>
|
||||
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>
|
||||
|
|
Loading…
Reference in New Issue