[gnome-continuous-yocto/gnomeostree-3.28-rocko: 8060/8267] bsp-guide: Changed dev-manual title name
- From: Emmanuele Bassi <ebassi src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-continuous-yocto/gnomeostree-3.28-rocko: 8060/8267] bsp-guide: Changed dev-manual title name
- Date: Sun, 17 Dec 2017 07:07:17 +0000 (UTC)
commit b93ebe5d4b67c5a31ac33aa504c2f55554098726
Author: Scott Rifenbark <srifenbark gmail com>
Date: Mon Oct 16 09:45:02 2017 -0700
bsp-guide: Changed dev-manual title name
Changes to all links to the dev-manual. This manual is now named
"Yocto Project Development Tasks Manual". There were some bad links
fixed as well. I had some links to some terms that used to be in the
dev-manual but are now in the ref-manual. Somehow they slipped by.
I have fixed those as well.
(From yocto-docs rev: b303190dd1234a7b83e0cd6217c69a449715062b)
Signed-off-by: Scott Rifenbark <srifenbark gmail com>
Signed-off-by: Richard Purdie <richard purdie linuxfoundation org>
documentation/bsp-guide/bsp.xml | 44 +++++++++++++++++++++-----------------
1 files changed, 24 insertions(+), 20 deletions(-)
---
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index 5db2837..e80c379 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -88,7 +88,7 @@
For more information on how to set up a local copy of source files
from a Git repository, see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#working-with-yocto-project-source-files'>Working With
Yocto Project Source Files</ulink>"
- section also in the Yocto Project Development Manual.
+ section also in the Yocto Project Development Tasks Manual.
</para>
<para>
@@ -139,7 +139,7 @@
<para>
For more detailed information on layers, see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#understanding-and-creating-layers'>Understanding and
Creating Layers</ulink>"
- section of the Yocto Project Development Manual.
+ section of the Yocto Project Development Tasks Manual.
</para>
</section>
@@ -164,7 +164,7 @@
Be sure you are set up to use BitBake in a shell.
See the
"<ulink
url='&YOCTO_DOCS_DEV_URL;#setting-up-the-development-host-to-use-the-yocto-project'>Setting Up the
Development Host to Use the Yocto Project</ulink>"
- section in the Yocto Project Development Manual for information
+ section in the Yocto Project Development Tasks Manual for information
on how to get a build host ready that is either a native
Linux machine or a machine that uses CROPS.
</para></listitem>
@@ -179,7 +179,7 @@
"<ulink url='&YOCTO_DOCS_DEV_URL;#checking-out-by-branch-in-poky'>Checking Out by
Branch in Poky</ulink>"
and
"<ulink url='&YOCTO_DOCS_DEV_URL;#checkout-out-by-tag-in-poky'>Checking Out by Tag
in Poky</ulink>"
- sections all in the Yocto Project Development Manual for
+ sections all in the Yocto Project Development Tasks Manual for
information on how to clone the <filename>poky</filename>
repository and check out the appropriate branch for your work.
</para></listitem>
@@ -236,7 +236,7 @@
For an example on how to discover branch names and
checkout on a branch, see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#checking-out-by-branch-in-poky'>Checking
Out By Branch in Poky</ulink>"
- section.
+ section in the Yocto Project Development Tasks Manual.
</para></listitem>
</orderedlist>
</para></listitem>
@@ -711,7 +711,7 @@
<para>
Tuning files are found in the <filename>meta/conf/machine/include</filename>
directory within the
- <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
+ <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>.
For example, the <filename>ia32-base.inc</filename> file resides in the
<filename>meta/conf/machine/include</filename> directory.
</para>
@@ -767,7 +767,7 @@
formfactor recipe
<filename>meta/recipes-bsp/formfactor/formfactor_0.0.bb</filename>,
which is found in the
- <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
+ <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>.
</para></note>
</section>
@@ -807,7 +807,7 @@
<para>
For your BSP, you typically want to use an existing Yocto
Project kernel recipe found in the
- <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>
+ <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>
at <filename>meta/recipes-kernel/linux</filename>.
You can append machine-specific changes to the kernel recipe
by using a similarly named append file, which is located in
@@ -928,7 +928,7 @@
about.
For more information on layers, see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#understanding-and-creating-layers'>Understanding
and Creating Layers</ulink>"
- section in the Yocto Project Development Manual.
+ section in the Yocto Project Development Tasks Manual.
For more information on BSP layers, see the
"<link linkend='bsp-layers'>BSP Layers</link>"
section.
@@ -1018,7 +1018,7 @@
of your new layer.
See the
"<ulink url='&YOCTO_DOCS_DEV_URL;#enabling-your-layer'>Enabling Your Layer</ulink>"
- section in the Yocto Project Development Manual
+ section in the Yocto Project Development Tasks Manual
for information on how to let the build system
know about your new layer.</para>
@@ -1070,24 +1070,28 @@
For guidelines on creating a layer that meets these base requirements, see the
"<link linkend='bsp-layers'>BSP Layers</link>" and the
"<ulink
url='&YOCTO_DOCS_DEV_URL;#understanding-and-creating-layers'>Understanding
- and Creating Layers"</ulink> in the Yocto Project Development
Manual.</para></listitem>
+ and Creating Layers"</ulink> in the Yocto Project Development Tasks Manual.
+ </para></listitem>
<listitem><para>The requirements in this section apply regardless of how you
package a BSP.
You should consult the packaging and distribution guidelines for your
specific release process.
For an example of packaging and distribution requirements, see the
"<ulink
url='https://wiki.yoctoproject.org/wiki/Third_Party_BSP_Release_Process'>Third Party BSP Release
Process</ulink>"
- wiki page.</para></listitem>
+ wiki page.
+ </para></listitem>
<listitem><para>The requirements for the BSP as it is made available to a developer
are completely independent of the released form of the BSP.
For example, the BSP Metadata can be contained within a Git repository
and could have a directory structure completely different from what appears
- in the officially released BSP layer.</para></listitem>
+ in the officially released BSP layer.
+ </para></listitem>
<listitem><para>It is not required that specific packages or package
modifications exist in the BSP layer, beyond the requirements for general
compliance with the Yocto Project.
For example, no requirement exists dictating that a specific kernel or
- kernel version be used in a given BSP.</para></listitem>
+ kernel version be used in a given BSP.
+ </para></listitem>
</itemizedlist>
</para>
@@ -1114,7 +1118,7 @@
<filename>recipes-*</filename> subdirectory.
You can find <filename>recipes.txt</filename> in the
<filename>meta</filename> directory of the
- <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>,
+ <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>,
or in the OpenEmbedded Core Layer
(<filename>openembedded-core</filename>) found at
<ulink url='http://git.openembedded.org/openembedded-core/tree/meta'></ulink>.
@@ -1171,7 +1175,7 @@
be sent.
For information on how to find the right person, see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#how-to-submit-a-change'>Submitting a
Change to the Yocto Project</ulink>"
- section in the Yocto Project Development Manual.
+ section in the Yocto Project Development Tasks Manual.
</para></listitem>
<listitem><para>Instructions on how to build the BSP using the BSP
layer.</para></listitem>
@@ -1275,7 +1279,7 @@
file for the modified recipe.
For information on using append files, see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#using-bbappend-files'>Using .bbappend Files in Your
Layer</ulink>"
- section in the Yocto Project Development Manual.
+ section in the Yocto Project Development Tasks Manual.
</para></listitem>
<listitem><para>
Ensure your directory structure in the BSP layer
@@ -1493,7 +1497,7 @@
<para>
Both tools reside in the <filename>scripts/</filename> subdirectory
- of the <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
+ of the <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>.
Consequently, to use the scripts, you must <filename>source</filename> the
environment just as you would when invoking a build:
<literallayout class='monospaced'>
@@ -1593,7 +1597,7 @@
a "generic" layer.
For information on this tool, see the
"<ulink
url='&YOCTO_DOCS_DEV_URL;#creating-a-general-layer-using-the-yocto-layer-script'>Creating a General Layer
Using the yocto-layer Script</ulink>"
- section in the Yocto Project Development Guide.
+ section in the Yocto Project Development Tasks Manual.
</note>
</para>
@@ -1743,7 +1747,7 @@
Defaults are accepted for each.</para></listitem>
<listitem><para>By default, the script creates the new BSP Layer in the
current working directory of the
- <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>,
+ <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>,
(i.e. <filename>poky/build</filename>).
</para></listitem>
</orderedlist>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
