mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-02-09 02:03:04 +01:00
Code Issues Packages Projects Releases Wiki Activity

documentation: Fixed links to old concepts-manual

Browse Source 
The concepts-manual is going away for 2.5.  I have fixed all the
links across the YP documentation set that were cross-referencing
into the concepts-manual so they now cross-reference into the
getting-started manual, where that concepts chapter will live
post 2.4x.

(From yocto-docs rev: e9145e9e7fef882a13c982d34514a94f864b3c12)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2018-04-10 12:04:20 -07:00
committed by Richard Purdie
parent b8bdf61ad1
commit 982cce2d2c
11 changed files with 131 additions and 122 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
documentation/bsp-guide/bsp.xml
View File

@@ -1687,9 +1687,10 @@
Thus, the build system can build the corresponding
recipe and include the component in the image.
See the
"<ulink url='&YOCTO_DOCS_CM_URL;#enabling-commercially-licensed-recipes'>Enabling Commercially Licensed Recipes</ulink>"
section in the Yocto Project Concepts Manual for
details on how to use these variables.</para>
"<ulink url='&YOCTO_DOCS_GS_URL;#enabling-commercially-licensed-recipes'>Enabling Commercially Licensed Recipes</ulink>"
section in the Yocto Project Overview and Concepts
Manual for details on how to use these variables.
</para>
<para>If you build as you normally would, without
specifying any recipes in the

42
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@@ -1872,8 +1872,8 @@
Your recipe must have a <filename>SRC_URI</filename> variable
that points to where the source is located.
For a graphical representation of source locations, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#sources-dev-environment'>Sources</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#sources-dev-environment'>Sources</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
<para>
@@ -2185,8 +2185,10 @@
containing the current checksum.
For more explanation and examples of how to set the
<filename>LIC_FILES_CHKSUM</filename> variable, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#usingpoky-configuring-LIC_FILES_CHKSUM'>Tracking License Changes</ulink>"
section in the Yocto Project Concepts Manual.</para>
"<ulink url='&YOCTO_DOCS_GS_URL;#usingpoky-configuring-LIC_FILES_CHKSUM'>Tracking License Changes</ulink>"
section in the Yocto Project Overview and Concepts
Manual.</para>
<para>To determine the correct checksum string, you
can list the appropriate files in the
<filename>LIC_FILES_CHKSUM</filename> variable with
@@ -2332,9 +2334,9 @@
automatically add a runtime dependency to "mypackage" on
"example").
See the
"<ulink url='&YOCTO_DOCS_CM_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
section in the Yocto Project Concepts Manual for further
details.
"<ulink url='&YOCTO_DOCS_GS_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
section in the Yocto Project Overview and Concepts Manual for
further details.
</para>
</section>
@@ -3396,9 +3398,10 @@
The variable
<filename><ulink url='&YOCTO_DOCS_REF_URL;#var-LIC_FILES_CHKSUM'>LIC_FILES_CHKSUM</ulink></filename>
is used to track source license changes as described in the
"<ulink url='&YOCTO_DOCS_CM_URL;#usingpoky-configuring-LIC_FILES_CHKSUM'>Tracking License Changes</ulink>"
section in the Yocto Project Concepts Manual.
You can quickly create Autotool-based recipes in a manner similar to the previous example.
"<ulink url='&YOCTO_DOCS_GS_URL;#usingpoky-configuring-LIC_FILES_CHKSUM'>Tracking License Changes</ulink>"
section in the Yocto Project Overview and Concepts Manual.
You can quickly create Autotool-based recipes in a manner
similar to the previous example.
</para>
</section>
@@ -3603,9 +3606,9 @@
allows runtime dependencies between packages
to be added automatically.
See the
"<ulink url='&YOCTO_DOCS_CM_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
section in the Yocto Project Concepts Manual
for more information.
"<ulink url='&YOCTO_DOCS_GS_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
section in the Yocto Project Overview and
Concepts Manual for more information.
</para></listitem>
</itemizedlist>
</note>
@@ -8503,7 +8506,7 @@ Some notes from Cal:
<para>
Because the OpenEmbedded build system uses
"<ulink url='&YOCTO_DOCS_CM_URL;#overview-checksums'>signatures</ulink>",
"<ulink url='&YOCTO_DOCS_GS_URL;#overview-checksums'>signatures</ulink>",
which are unique to a given build, the build system
knows when to rebuild packages.
All the inputs into a given task are represented by a
@@ -8607,8 +8610,9 @@ Some notes from Cal:
<para>
For more information on shared state, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#shared-state-cache'>Shared State Cache</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#shared-state-cache'>Shared State Cache</ulink>"
section in the Yocto Project Overview and Concepts
Manual.
</para>
</note>
</section>
@@ -12257,7 +12261,7 @@ Some notes from Cal:
${BUILDDIR}/tmp/stamps/i586-poky-linux/db/6.0.30-r1.do_fetch.sigdata.7c048c18222b16ff0bcee2000ef648b1
</literallayout>
For tasks that are accelerated through the shared state
(<ulink url='&YOCTO_DOCS_CM_URL;#shared-state-cache'>sstate</ulink>)
(<ulink url='&YOCTO_DOCS_GS_URL;#shared-state-cache'>sstate</ulink>)
cache, an additional <filename>siginfo</filename> file
is written into
<ulink url='&YOCTO_DOCS_REF_URL;#var-SSTATE_DIR'><filename>SSTATE_DIR</filename></ulink>
@@ -12366,8 +12370,8 @@ Some notes from Cal:
<filename>-c</filename>, BitBake will only run the task if it
considers it "out of date".
See the
"<ulink url='&YOCTO_DOCS_CM_URL;#stamp-files-and-the-rerunning-of-tasks'>Stamp Files and the Rerunning of Tasks</ulink>"
section in the Yocto Project Concepts Manual for
"<ulink url='&YOCTO_DOCS_GS_URL;#stamp-files-and-the-rerunning-of-tasks'>Stamp Files and the Rerunning of Tasks</ulink>"
section in the Yocto Project Overview and Concepts Manual for
how BitBake determines whether a task is "out of date".
</para>

4
documentation/dev-manual/dev-manual-start.xml
View File

@@ -748,8 +748,8 @@
<ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>
under <filename>tmp/deploy/images</filename>.
For detailed information on the build process using BitBake, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#images-dev-environment'>Images</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#images-dev-environment'>Images</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
<para>

2
documentation/getting-started/getting-started-concepts.xml
View File

@@ -1567,7 +1567,7 @@
<ulink url='&YOCTO_DOCS_REF_URL;#var-STAMP'><filename>STAMP</filename></ulink>
variable, and the end of the name consists of the task's
name and current
<ulink url='&YOCTO_DOCS_CM_URL;#overview-checksums'>input checksum</ulink>.
<ulink url='&YOCTO_DOCS_GS_URL;#overview-checksums'>input checksum</ulink>.
<note>
This naming scheme assumes that
<ulink url='&YOCTO_DOCS_BB_URL;#var-BB_SIGNATURE_HANDLER'><filename>BB_SIGNATURE_HANDLER</filename></ulink>

9
documentation/getting-started/getting-started-yp-intro.xml
View File

@@ -654,8 +654,9 @@
when they do not.</para>
<para>You can read more about Pseudo in the
"<ulink url='&YOCTO_DOCS_CM_URL;#fakeroot-and-pseudo'>Fakeroot and Pseudo</ulink>"
section of the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#fakeroot-and-pseudo'>Fakeroot and Pseudo</ulink>"
section of the Yocto Project Overview and Concepts
Manual.
</para></listitem>
</itemizedlist>
</para>
@@ -1142,8 +1143,8 @@
<para>
For a very detailed look at this workflow, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#development-concepts'>Development Concepts</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#development-concepts'>Development Concepts</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</section>

28
documentation/ref-manual/ref-classes.xml
View File

@@ -568,9 +568,9 @@
provides support for the recipes that build the Canadian
Cross-compilation tools for SDKs.
See the
"<ulink url='&YOCTO_DOCS_CM_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>"
section in the Yocto Project Concepts Manual for more discussion on
these cross-compilation tools.
"<ulink url='&YOCTO_DOCS_GS_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>"
section in the Yocto Project Overview and Concepts Manual for more
discussion on these cross-compilation tools.
</para>
</section>
@@ -582,9 +582,9 @@
provides support for the recipes that build the cross-compilation
tools used for building SDKs.
See the
"<ulink url='&YOCTO_DOCS_CM_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>"
section in the Yocto Project Concepts Manual for more discussion on
these cross-compilation tools.
"<ulink url='&YOCTO_DOCS_GS_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>"
section in the Yocto Project Overview and Concepts Manual for more
discussion on these cross-compilation tools.
</para>
</section>
@@ -1251,8 +1251,8 @@
"<ulink url='&YOCTO_DOCS_DEV_URL;#usingpoky-extend-customimage'>Customizing Images</ulink>"
section in the Yocto Project Development Tasks Manual.
For information on how images are created, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#images-dev-environment'>Images</ulink>"
section in the Yocto Project Concpets Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#images-dev-environment'>Images</ulink>"
section in the Yocto Project Overview and Concpets Manual.
</para>
</section>
@@ -2722,8 +2722,8 @@ This check was removed for YP 2.3 release
<para>
For more information on the cross-development toolchain
generation, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GM_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>"
section in the Yocto Project Overview and Concepts Manual.
For information on advantages gained when building a
cross-development toolchain using the
<link linkend='ref-tasks-populate_sdk'><filename>do_populate_sdk</filename></link>
@@ -3020,8 +3020,8 @@ This check was removed for YP 2.3 release
<para>
For information on how root filesystem images are created, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#image-generation-dev-environment'>Image Generation</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#image-generation-dev-environment'>Image Generation</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</section>
@@ -3182,8 +3182,8 @@ This check was removed for YP 2.3 release
<para>
For more information on sstate, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#shared-state-cache'>Shared State Cache</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#shared-state-cache'>Shared State Cache</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</section>

4
documentation/ref-manual/ref-images.xml
View File

@@ -151,8 +151,8 @@
This image provides the Wayland protocol libraries and the
reference Weston compositor.
For more information, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#wayland'>Wayland</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#wayland'>Wayland</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para></listitem>
<listitem><para><filename>core-image-x11</filename>:
A very basic X11 image with a terminal.

10
documentation/ref-manual/ref-structure.xml
View File

@@ -520,10 +520,10 @@
variable points to this directory.
For more detail on the contents of the <filename>deploy</filename>
directory, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#images-dev-environment'>Images</ulink>"
"<ulink url='&YOCTO_DOCS_GS_URL;#images-dev-environment'>Images</ulink>"
and
"<ulink url='&YOCTO_DOCS_CM_URL;#sdk-dev-environment'>Application Development SDK</ulink>"
sections in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#sdk-dev-environment'>Application Development SDK</ulink>"
sections in the Yocto Project Overview and Concepts Manual.
</para>
</section>
@@ -696,8 +696,8 @@
<para>
For information on how BitBake uses stamp files to determine if
a task should be rerun, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#stamp-files-and-the-rerunning-of-tasks'>Stamp Files and the Rerunning of Tasks</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#stamp-files-and-the-rerunning-of-tasks'>Stamp Files and the Rerunning of Tasks</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</section>

56
documentation/ref-manual/ref-tasks.xml
View File

@@ -220,8 +220,8 @@
<para>
For more information on image creation, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#image-generation-dev-environment'>Image Generation</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#image-generation-dev-environment'>Image Generation</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</section>
@@ -246,8 +246,8 @@
<para>
For more information on image creation, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#image-generation-dev-environment'>Image Generation</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#image-generation-dev-environment'>Image Generation</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</section>
@@ -268,7 +268,7 @@
and
<link linkend='ref-tasks-rootfs'><filename>do_rootfs</filename></link>),
run under
<ulink url='&YOCTO_DOCS_CM_URL;#fakeroot-and-pseudo'>fakeroot</ulink>.
<ulink url='&YOCTO_DOCS_GS_URL;#fakeroot-and-pseudo'>fakeroot</ulink>.
<note>
<title>Caution</title>
@@ -342,8 +342,8 @@
For additional information, see the
<link linkend='var-PKGDESTWORK'><filename>PKGDESTWORK</filename></link>
variable and the
"<ulink url='&YOCTO_DOCS_CM_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</section>
@@ -367,8 +367,8 @@
<filename>${</filename><link linkend='var-DEPLOY_DIR_DEB'><filename>DEPLOY_DIR_DEB</filename></link><filename>}</filename>
directory in the package feeds area.
For more information, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</section>
@@ -381,8 +381,8 @@
<filename>${</filename><link linkend='var-DEPLOY_DIR_IPK'><filename>DEPLOY_DIR_IPK</filename></link><filename>}</filename>
directory in the package feeds area.
For more information, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</section>
@@ -395,8 +395,8 @@
<filename>${</filename><link linkend='var-DEPLOY_DIR_RPM'><filename>DEPLOY_DIR_RPM</filename></link><filename>}</filename>
directory in the package feeds area.
For more information, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</section>
@@ -408,8 +408,8 @@
<filename>${</filename><link linkend='var-DEPLOY_DIR_TAR'><filename>DEPLOY_DIR_TAR</filename></link><filename>}</filename>
directory in the package feeds area.
For more information, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</section>
@@ -431,8 +431,8 @@
<para>
Locates patch files and applies them to the source code.
See the
"<ulink url='&YOCTO_DOCS_CM_URL;#patching-dev-environment'>Patching</ulink>"
section in the Yocto Project Concepts Manual for more
"<ulink url='&YOCTO_DOCS_GS_URL;#patching-dev-environment'>Patching</ulink>"
section in the Yocto Project Overview and Concepts Manual for more
information.
</para>
</section>
@@ -452,8 +452,8 @@
<para>
Creates the file and directory structure for an installable SDK.
See the
"<ulink url='&YOCTO_DOCS_CM_URL;#sdk-generation-dev-environment'>SDK Generation</ulink>"
section in the Yocto Project Concepts Manual for more
"<ulink url='&YOCTO_DOCS_GS_URL;#sdk-generation-dev-environment'>SDK Generation</ulink>"
section in the Yocto Project Overview and Concepts Manual for more
information.
</para>
</section>
@@ -540,8 +540,8 @@
<link linkend='var-S'><filename>S</filename></link> variable also
plays a role in where unpacked source files ultimately reside.
For more information on how source files are unpacked, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#source-fetching-dev-environment'>Source Fetching</ulink>"
section in the Yocto Project Concepts Manual and also
"<ulink url='&YOCTO_DOCS_GS_URL;#source-fetching-dev-environment'>Source Fetching</ulink>"
section in the Yocto Project Overview and Concepts Manual and also
see the <filename>WORKDIR</filename> and
<filename>S</filename> variable descriptions.
</para>
@@ -620,7 +620,7 @@
<para>
Running this task does not remove the
<ulink url='&YOCTO_DOCS_CM_URL;#shared-state-cache'>sstate</ulink>
<ulink url='&YOCTO_DOCS_GS_URL;#shared-state-cache'>sstate</ulink>
cache files.
Consequently, if no changes have been made and the recipe is
rebuilt after cleaning, output files are simply restored from the
@@ -637,7 +637,7 @@
<para>
Removes all output files, shared state
(<ulink url='&YOCTO_DOCS_CM_URL;#shared-state-cache'>sstate</ulink>)
(<ulink url='&YOCTO_DOCS_GS_URL;#shared-state-cache'>sstate</ulink>)
cache, and downloaded source files for a target (i.e. the contents
of
<link linkend='var-DL_DIR'><filename>DL_DIR</filename></link>).
@@ -668,13 +668,13 @@
<para>
Removes all output files and shared state
(<ulink url='&YOCTO_DOCS_CM_URL;#shared-state-cache'>sstate</ulink>)
(<ulink url='&YOCTO_DOCS_GS_URL;#shared-state-cache'>sstate</ulink>)
cache for a target.
Essentially, the <filename>do_cleansstate</filename> task is
identical to the
<link linkend='ref-tasks-clean'><filename>do_clean</filename></link>
task with the added removal of shared state
(<ulink url='&YOCTO_DOCS_CM_URL;#shared-state-cache'>sstate</ulink>)
(<ulink url='&YOCTO_DOCS_GS_URL;#shared-state-cache'>sstate</ulink>)
cache.
</para>
@@ -744,7 +744,7 @@
<para>
Creates or updates the index in the
<ulink url='&YOCTO_DOCS_CM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>
<ulink url='&YOCTO_DOCS_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>
area.
<note>
This task is not triggered with the
@@ -796,8 +796,8 @@
Creates the root filesystem (file and directory structure) for an
image.
See the
"<ulink url='&YOCTO_DOCS_CM_URL;#image-generation-dev-environment'>Image Generation</ulink>"
section in the Yocto Project Concepts Manual for more
"<ulink url='&YOCTO_DOCS_GS_URL;#image-generation-dev-environment'>Image Generation</ulink>"
section in the Yocto Project Overview and Concepts Manual for more
information on how the root filesystem is created.
</para>
</section>

4
documentation/ref-manual/ref-terms.xml
View File

@@ -200,8 +200,8 @@
<para>Creation of these toolchains is simple and automated.
For information on toolchain concepts as they apply to the
Yocto Project, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>"
section in the Yocto Project Overview and Concepts Manual.
You can also find more information on using the
relocatable toolchain in the
<ulink url='&YOCTO_DOCS_SDK_URL;'>Yocto Project Application Development and the Extensible Software Development Kit (eSDK)</ulink>

87
documentation/ref-manual/ref-variables.xml
View File

@@ -3017,7 +3017,7 @@
<note><title>Caution</title>
Tasks that read from or write to this directory should
run under
<ulink url='&YOCTO_DOCS_CM_URL;#fakeroot-and-pseudo'>fakeroot</ulink>.
<ulink url='&YOCTO_DOCS_GS_URL;#fakeroot-and-pseudo'>fakeroot</ulink>.
</note>
</para>
</glossdef>
@@ -3264,10 +3264,10 @@
add any runtime dependencies between the
packages produced by the two recipes.
However, as explained in the
"<ulink url='&YOCTO_DOCS_CM_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
section in the Yocto Project Concepts Manual,
runtime dependencies will often be
added automatically, meaning
"<ulink url='&YOCTO_DOCS_GS_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
section in the Yocto Project Overview and
Concepts Manual, runtime dependencies will
often be added automatically, meaning
<filename>DEPENDS</filename> alone is
sufficient for most recipes.
</para></listitem>
@@ -3329,11 +3329,12 @@
section.
For more detail on the contents of the
<filename>deploy</filename> directory, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#images-dev-environment'>Images</ulink>",
"<ulink url='&YOCTO_DOCS_CM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>",
"<ulink url='&YOCTO_DOCS_GS_URL;#images-dev-environment'>Images</ulink>",
"<ulink url='&YOCTO_DOCS_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>",
and
"<ulink url='&YOCTO_DOCS_CM_URL;#sdk-dev-environment'>Application Development SDK</ulink>"
sections all in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#sdk-dev-environment'>Application Development SDK</ulink>"
sections all in the Yocto Project Overview and Concepts
Manual.
</para>
</glossdef>
</glossentry>
@@ -3372,8 +3373,8 @@
<link linkend='ref-tasks-package_write_deb'><filename>do_package_write_deb</filename></link>
task writes Debian packages into the appropriate folder.
For more information on how packaging works, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</glossdef>
</glossentry>
@@ -3402,10 +3403,11 @@
section.
For more detail on the contents of the
<filename>deploy</filename> directory, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#images-dev-environment'>Images</ulink>"
"<ulink url='&YOCTO_DOCS_GS_URL;#images-dev-environment'>Images</ulink>"
and
"<ulink url='&YOCTO_DOCS_CM_URL;#sdk-dev-environment'>Application Development SDK</ulink>"
sections both in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#sdk-dev-environment'>Application Development SDK</ulink>"
sections both in the Yocto Project Overview and Concepts
Manual.
</para>
</glossdef>
</glossentry>
@@ -3443,8 +3445,8 @@
<link linkend='ref-tasks-package_write_ipk'><filename>do_package_write_ipk</filename></link>
task writes IPK packages into the appropriate folder.
For more information on how packaging works, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</glossdef>
</glossentry>
@@ -3482,8 +3484,8 @@
<link linkend='ref-tasks-package_write_rpm'><filename>do_package_write_rpm</filename></link>
task writes RPM packages into the appropriate folder.
For more information on how packaging works, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</glossdef>
</glossentry>
@@ -3521,8 +3523,8 @@
<link linkend='ref-tasks-package_write_tar'><filename>do_package_write_tar</filename></link>
task writes TAR packages into the appropriate folder.
For more information on how packaging works, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</glossdef>
</glossentry>
@@ -6104,8 +6106,8 @@
variables.
You can find information on how the image
is created in the
"<ulink url='&YOCTO_DOCS_CM_URL;#image-generation-dev-environment'>Image Generation</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#image-generation-dev-environment'>Image Generation</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</glossdef>
</glossentry>
@@ -7978,8 +7980,8 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
<link linkend='var-LICENSE'><filename>LICENSE</filename></link>
is set to "CLOSED").</para>
<para>For more information, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#usingpoky-configuring-LIC_FILES_CHKSUM'>Tracking License Changes</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#usingpoky-configuring-LIC_FILES_CHKSUM'>Tracking License Changes</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</glossdef>
</glossentry>
@@ -8114,8 +8116,8 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
require additional licenses in order to be used in a
commercial product.
For more information, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#enabling-commercially-licensed-recipes'>Enabling Commercially Licensed Recipes</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#enabling-commercially-licensed-recipes'>Enabling Commercially Licensed Recipes</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</glossdef>
</glossentry>
@@ -8134,8 +8136,8 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
This practice is otherwise known as "whitelisting"
license flags.
For more information, see the
<ulink url='&YOCTO_DOCS_CM_URL;#enabling-commercially-licensed-recipes'>Enabling Commercially Licensed Recipes</ulink>"
section in the Yocto Project Concepts Manual.
<ulink url='&YOCTO_DOCS_GS_URL;#enabling-commercially-licensed-recipes'>Enabling Commercially Licensed Recipes</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</glossdef>
</glossentry>
@@ -10488,8 +10490,9 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
${STAGING_DIR_HOST}/pkgdata
</literallayout>
For examples of how this data is used, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
section in the Yocto Project Concepts Manual and the
"<ulink url='&YOCTO_DOCS_GS_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
section in the Yocto Project Overview and Concepts Manual
and the
"<ulink url='&YOCTO_DOCS_DEV_URL;#viewing-package-information-with-oe-pkgdata-util'>Viewing Package Information with <filename>oe-pkgdata-util</filename></ulink>"
section in the Yocto Project Development Tasks Manual.
</para>
@@ -10735,11 +10738,11 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
<filename>PR</filename> to know when to rebuild a
recipe.
The build system uses the task
<ulink url='&YOCTO_DOCS_CM_URL;#overview-checksums'>input checksums</ulink>
<ulink url='&YOCTO_DOCS_GS_URL;#overview-checksums'>input checksums</ulink>
along with the
<link linkend='structure-build-tmp-stamps'>stamp</link>
and
<ulink url='&YOCTO_DOCS_CM_URL;#shared-state-cache'>shared state cache</ulink>
<ulink url='&YOCTO_DOCS_GS_URL;#shared-state-cache'>shared state cache</ulink>
mechanisms.
</note>
The <filename>PR</filename> variable primarily becomes
@@ -11008,8 +11011,8 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
<para>
For more information, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
</glossdef>
</glossentry>
@@ -11325,8 +11328,8 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
Therefore, most recipes do not need to set
<filename>RDEPENDS</filename>.
For more information, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
<para>
@@ -13845,8 +13848,8 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
<para>
For information on how BitBake uses stamp files to determine
if a task should be rerun, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#stamp-files-and-the-rerunning-of-tasks'>Stamp Files and the Rerunning of Tasks</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#stamp-files-and-the-rerunning-of-tasks'>Stamp Files and the Rerunning of Tasks</ulink>"
section in the Yocto Project Overview and Concepts Manual.
</para>
<para>
@@ -15337,8 +15340,8 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
<para>
For background information on cross-development toolchains
in the Yocto Project development environment, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>"
section in the Yocto Project Overview and Concepts Manual.
For information on setting up a cross-development
environment, see the
<ulink url='&YOCTO_DOCS_SDK_URL;'>Yocto Project Application Development and the Extensible Software Development Kit (eSDK)</ulink>
@@ -15396,8 +15399,8 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
<para>
For background information on cross-development toolchains
in the Yocto Project development environment, see the
"<ulink url='&YOCTO_DOCS_CM_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>"
section in the Yocto Project Concepts Manual.
"<ulink url='&YOCTO_DOCS_GS_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>"
section in the Yocto Project Overview and Concepts Manual.
For information on setting up a cross-development
environment, see the
<ulink url='&YOCTO_DOCS_SDK_URL;'>Yocto Project Application Development and the Extensible Software Development Kit (eSDK)</ulink>