bitbake: bitbake-user-manual-metadata.xml: KERNEL_FEATURES example updated.

I added text to separate this example code from the general
BitBake User Manual's spirit of standing alone and away from
YP or OE stuff.  Also, added another space to move the examples
code so that 5 spaces are used for literal indentation.

(Bitbake rev: 17fcac8a7b21afa5c7d201e94cbf603ab07ba70c)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark authored and Richard Purdie committed 2014-07-21 11:00:58 +01:00
1 parent c723fa02f6
commit 335defe010
1 file changed
+5 -4
@@ -438,14 +438,15 @@
</para>
<para>
Again using a kernel recipe file as an example, the
Again, using an OpenEmbedded metadata-based
kernel recipe file as an example, the
following lines will conditionally append to the
<filename>KERNEL_FEATURES</filename> variable based
on the architecture:
<literallayout class='monospaced'>
KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc"
KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc"
</literallayout>
</para></listitem>
</itemizedlist>