</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>
</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>