bsp-guide, kernel-dev: Added Cross-references to "BitBake" term

I made sure that the first occurrence of each "BitBake" term linked
into the "BitBake" term as defined in the dev-manual.

(From yocto-docs rev: 83e6e43d13cf5447b8ef65836d532abbb1f8b15e)

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
2014-03-28 06:46:04 -06:00
committed by Richard Purdie
parent df02dd8c65
commit 338b500fa8
3 changed files with 16 additions and 10 deletions

View File

@@ -339,7 +339,9 @@
</para>
<para>
This file simply makes BitBake aware of the recipes and configuration directories.
This file simply makes
<ulink url='&YOCTO_DOCS_DEV_URL;#bitbake-term'>BitBake</ulink>
aware of the recipes and configuration directories.
The file must exist so that the OpenEmbedded build system can recognize the BSP.
</para>
</section>

View File

@@ -47,7 +47,9 @@
variable.
This variable is typically set to the same value as the
<ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
variable, which is used by BitBake (e.g. "routerstationpro" or "fri2").
variable, which is used by
<ulink url='&YOCTO_DOCS_DEV_URL;#bitbake-term'>BitBake</ulink>
(e.g. "routerstationpro" or "fri2").
Multiple BSPs can reuse the same <filename>KMACHINE</filename>
name if they are built using the same BSP description.
The "fri2" and "fri2-noemgd" BSP combination

View File

@@ -25,7 +25,9 @@
If you are going to be modifying kernel recipes, it is recommended
that you create and prepare your own layer in which to do your
work.
Your layer contains its own BitBake append files
Your layer contains its own
<ulink url='&YOCTO_DOCS_DEV_URL;#bitbake-term'>BitBake</ulink>
append files
(<filename>.bbappend</filename>) and provides a convenient
mechanism to create your own recipe files
(<filename>.bb</filename>).