1
0
mirror of https://git.yoctoproject.org/poky synced 2026-05-30 12:29:55 +00:00

documentation/bsp-guide/bsp.xml: Fixed some links.

Some areas didn't checkout with the first pass of applying the
poky.ent variables.  I cleaned these up.

(From yocto-docs rev: 9a3b82b8801ce70d2cc22e7dc5630d06f603d2ea)

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
2012-06-15 05:42:02 -07:00
committed by Richard Purdie
parent 9622701c00
commit 74b0cafd65
+5 -8
View File
@@ -48,7 +48,7 @@
This root is what you add to the This root is what you add to the
<ulink url='&YOCTO_DOCS_REF_URL;#var-BBLAYERS'><filename>BBLAYERS</filename></ulink> <ulink url='&YOCTO_DOCS_REF_URL;#var-BBLAYERS'><filename>BBLAYERS</filename></ulink>
variable in the <filename>conf/bblayers.conf</filename> file found in the variable in the <filename>conf/bblayers.conf</filename> file found in the
<ulink url='&YOCTO_DOCS_DEV_URL;#yocto-project-build-directory'>Yocto Project Build Directory</ulink>. Yocto Project Build Directory.
Adding the root allows the Yocto Project build system to recognize the BSP Adding the root allows the Yocto Project build system to recognize the BSP
definition and from it build an image. definition and from it build an image.
Here is an example: Here is an example:
@@ -614,8 +614,7 @@
The configuration options will likely end up in that location anyway if the BSP gets The configuration options will likely end up in that location anyway if the BSP gets
added to the Yocto Project. added to the Yocto Project.
For information on how to add these configurations directly, see For information on how to add these configurations directly, see
<ulink url='http://yoctoproject.org/docs/1.1.1/kernel-manual/kernel-manual.html'> <ulink url='&YOCTO_DOCS_KERNEL_URL;'>The Yocto Project Kernel Architecture and Use Manual</ulink>.</para>
The Yocto Project Kernel Architecture and Use Manual</ulink>.</para>
<para> <para>
In general, however, the Yocto Project maintainers take care of moving the In general, however, the Yocto Project maintainers take care of moving the
<filename>SRC_URI</filename>-specified <filename>SRC_URI</filename>-specified
@@ -695,8 +694,7 @@
<filename>recipe-*</filename> subdirectory. <filename>recipe-*</filename> subdirectory.
You can find <filename>recipes.txt</filename> in the You can find <filename>recipes.txt</filename> in the
<filename>meta</filename> directory of the <filename>meta</filename> directory of the
<ulink url='&YOCTO_DOCS_DEV_URL;#yocto-project-files'>Yocto Yocto Project Files, or in the OpenEmbedded Core Layer
Project Files</ulink>, or in the OpenEmbedded Core Layer
(<filename>openembedded-core</filename>) found at (<filename>openembedded-core</filename>) found at
<ulink url='http://git.openembedded.org/openembedded-core/tree/meta'></ulink>. <ulink url='http://git.openembedded.org/openembedded-core/tree/meta'></ulink>.
</para> </para>
@@ -835,7 +833,7 @@
Basing your recipes on these kernels reduces the costs for maintaining Basing your recipes on these kernels reduces the costs for maintaining
the BSP and increases its scalability. the BSP and increases its scalability.
See the <filename>Yocto Linux Kernel</filename> category in the See the <filename>Yocto Linux Kernel</filename> category in the
<ulink url='&YOCTO_GIT_URL;/cgit.cgi'><filename>Yocto Source Repositories</filename></ulink> <ulink url='&YOCTO_GIT_URL;/cgit.cgi'>Yocto Source Repositories</ulink>
for these kernels.</para></listitem> for these kernels.</para></listitem>
</itemizedlist> </itemizedlist>
</para> </para>
@@ -1027,8 +1025,7 @@
<para> <para>
Both tools reside in the <filename>scripts/</filename> subdirectory Both tools reside in the <filename>scripts/</filename> subdirectory
of the <ulink url='&YOCTO_DOCS_DEV_URL;#yocto-project-files'>Yocto Project of the Yocto Project Files.
Files</ulink>.
Consequently, to use the scripts, you must <filename>source</filename> the Consequently, to use the scripts, you must <filename>source</filename> the
environment just as you would when invoking a build: environment just as you would when invoking a build:
<literallayout class='monospaced'> <literallayout class='monospaced'>