From 338b500fa872ded0053bb78080d9c9ffdc232b19 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Fri, 28 Mar 2014 06:46:04 -0600
Subject: 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>
---
documentation/kernel-dev/kernel-dev-advanced.xml | 18 ++++++++++--------
documentation/kernel-dev/kernel-dev-common.xml | 4 +++-
2 files changed, 13 insertions(+), 9 deletions(-)
(limited to 'documentation/kernel-dev')
diff --git a/documentation/kernel-dev/kernel-dev-advanced.xml b/documentation/kernel-dev/kernel-dev-advanced.xml
index 4589e4b9fc..64d8110576 100644
--- a/documentation/kernel-dev/kernel-dev-advanced.xml
+++ b/documentation/kernel-dev/kernel-dev-advanced.xml
@@ -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
@@ -298,16 +300,16 @@
</para>
<para>
- If you modify the Metadata in the linux-yocto
- <filename>meta</filename> branch, you must not forget to update
- the
+ If you modify the Metadata in the linux-yocto
+ <filename>meta</filename> branch, you must not forget to update
+ the
<ulink url='&YOCTO_DOCS_REF_URL;#var-SRCREV'><filename>SRCREV</filename></ulink>
statements in the kernel's recipe.
- In particular, you need to update the
- <filename>SRCREV_meta</filename> variable to match the commit in
+ In particular, you need to update the
+ <filename>SRCREV_meta</filename> variable to match the commit in
the <filename>KMETA</filename> branch you wish to use.
- Changing the data in these branches and not updating the
- <filename>SRCREV</filename> statements to match will cause the
+ Changing the data in these branches and not updating the
+ <filename>SRCREV</filename> statements to match will cause the
build to fetch an older commit.
</para>
</section>
diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml
index f73f981ce8..ef1d0dbc5b 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -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>).
--
cgit v1.2.3-54-g00ecf