diff options
author | Scott Rifenbark <srifenbark@gmail.com> | 2018-04-12 10:57:32 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-05-24 17:16:13 +0100 |
commit | 1b877bc9dd3e9048489e6868020876af812cfa5e (patch) | |
tree | fa48122df594b4477be6529f51cf5f9255ebaaef /documentation | |
parent | 7105c52799c506961ec59e28681d8d6b588ffb4a (diff) | |
download | openembedded-core-contrib-1b877bc9dd3e9048489e6868020876af812cfa5e.tar.gz |
documentation: Updated everything for new overview-manual
This involved changing the root manual folder from
"getting-started" to "overview-manual".
Also, every link using the ENTITY "YOCTO_DOCS_GS_URL" was
changed to "YOCTO_DOCS_OM_URL". Most manuals had several
occurrences of these links.
The makefile needed updating to process the new manual
and not process the old "getting-started" manual.
(From yocto-docs rev: 1abf64e56e9096258038ae37b787a81bf786bb3b)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
26 files changed, 118 insertions, 122 deletions
diff --git a/documentation/Makefile b/documentation/Makefile index 4423807580..df0a18dacb 100644 --- a/documentation/Makefile +++ b/documentation/Makefile @@ -90,7 +90,7 @@ XSLTOPTS = --stringparam html.stylesheet brief-yoctoprojectqs-style.css \ --stringparam section.autolabel 0 \ --stringparam section.label.includes.component.label 0 \ --xinclude -ALLPREQ = html tarball +ALLPREQ = html eclipse tarball TARFILES = brief-yoctoprojectqs-style.css brief-yoctoprojectqs.html figures/bypqs-title.png \ figures/yocto-project-transp.png MANUALS = $(DOC)/$(DOC).html $(DOC)/eclipse diff --git a/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.xml b/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.xml index d9960398f5..116dfbd145 100644 --- a/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.xml +++ b/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.xml @@ -52,7 +52,7 @@ <para> If you want more conceptual or background information on the Yocto Project, see the - <ulink url='&YOCTO_DOCS_GS_URL;'>Yocto Project Overview and Concepts Manual</ulink>. + <ulink url='&YOCTO_DOCS_OM_URL;'>Yocto Project Overview and Concepts Manual</ulink>. </para> </section> @@ -242,7 +242,7 @@ </literallayout> For information on using the <filename>bitbake</filename> command, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#usingpoky-components-bitbake'>BitBake</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#usingpoky-components-bitbake'>BitBake</ulink>" section in the Yocto Project Overview and Concepts Manual, or see the "<ulink url='&YOCTO_DOCS_BB_URL;#bitbake-user-manual-command'>BitBake Command</ulink>" @@ -302,7 +302,7 @@ <listitem><para> <emphasis>Yocto Project Overview and Concepts Manual:</emphasis> The - <ulink url='&YOCTO_DOCS_GS_URL;'>Yocto Project Overview and Concepts Manual</ulink> + <ulink url='&YOCTO_DOCS_OM_URL;'>Yocto Project Overview and Concepts Manual</ulink> is a great place to start to learn about the Yocto Project. This manual introduces you to the Yocto Project and its diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index 200aed1899..a1908d38c3 100644 --- a/documentation/bsp-guide/bsp.xml +++ b/documentation/bsp-guide/bsp.xml @@ -56,7 +56,7 @@ To help understand the BSP layer concept, consider the BSPs that the Yocto Project supports and provides with each release. You can see the layers in the - <ulink url='&YOCTO_DOCS_GS_URL;#yocto-project-repositories'>Yocto Project Source Repositories</ulink> + <ulink url='&YOCTO_DOCS_OM_URL;#yocto-project-repositories'>Yocto Project Source Repositories</ulink> through a web interface at <ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi'></ulink>. If you go to that interface, you will find a list of repositories @@ -340,7 +340,7 @@ It is also intended that it will be be simple to extract information and convert it to other formats if required. The OpenEmbedded build system, through its standard - <ulink url='&YOCTO_DOCS_GS_URL;#the-yocto-project-layer-model'>layers mechanism</ulink>, + <ulink url='&YOCTO_DOCS_OM_URL;#the-yocto-project-layer-model'>layers mechanism</ulink>, can directly accept the format described as a layer. The BSP layer captures all the hardware-specific details in one place using a standard format, which is useful @@ -1056,7 +1056,7 @@ information for the project that the OpenEmbedded build system knows about. For more information on layers, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#the-yocto-project-layer-model'>The Yocto Project Layer Model</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#the-yocto-project-layer-model'>The Yocto Project Layer Model</ulink>" section in the Yocto Project Overview and Concepts Manual. You can also reference the @@ -1687,7 +1687,7 @@ Thus, the build system can build the corresponding recipe and include the component in the image. See the - "<ulink url='&YOCTO_DOCS_GS_URL;#enabling-commercially-licensed-recipes'>Enabling Commercially Licensed Recipes</ulink>" + "<ulink url='&YOCTO_DOCS_OM_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> diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index fd1734beec..85b3a4a8a2 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -24,7 +24,7 @@ each other. For introductory information on the Yocto Project Layer Model, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#the-yocto-project-layer-model'>The Yocto Project Layer Model</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#the-yocto-project-layer-model'>The Yocto Project Layer Model</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> @@ -1855,7 +1855,7 @@ <para> You can find more information about the build process in - "<ulink url='&YOCTO_DOCS_GS_URL;#overview-development-environment'>The Yocto Project Development Environment</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#overview-development-environment'>The Yocto Project Development Environment</ulink>" chapter of the Yocto Project Overview and Concepts Manual. </para> </section> @@ -1872,7 +1872,7 @@ 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_GS_URL;#sources-dev-environment'>Sources</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#sources-dev-environment'>Sources</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> @@ -2185,7 +2185,7 @@ 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_GS_URL;#usingpoky-configuring-LIC_FILES_CHKSUM'>Tracking License Changes</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#usingpoky-configuring-LIC_FILES_CHKSUM'>Tracking License Changes</ulink>" section in the Yocto Project Overview and Concepts Manual.</para> @@ -2334,7 +2334,7 @@ automatically add a runtime dependency to "mypackage" on "example"). See the - "<ulink url='&YOCTO_DOCS_GS_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>" section in the Yocto Project Overview and Concepts Manual for further details. </para> @@ -3398,7 +3398,7 @@ 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_GS_URL;#usingpoky-configuring-LIC_FILES_CHKSUM'>Tracking License Changes</ulink>" + "<ulink url='&YOCTO_DOCS_OM_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. @@ -3606,7 +3606,7 @@ allows runtime dependencies between packages to be added automatically. See the - "<ulink url='&YOCTO_DOCS_GS_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>" section in the Yocto Project Overview and Concepts Manual for more information. </para></listitem> @@ -6347,7 +6347,7 @@ can use an existing file provided by the Wic installation. As shipped, kickstart files can be found in the Yocto Project - <ulink url='&YOCTO_DOCS_GS_URL;#source-repositories'>Source Repositories</ulink> + <ulink url='&YOCTO_DOCS_OM_URL;#source-repositories'>Source Repositories</ulink> in the following two locations: <literallayout class='monospaced'> poky/meta-yocto-bsp/wic @@ -8506,7 +8506,7 @@ Some notes from Cal: <para> Because the OpenEmbedded build system uses - "<ulink url='&YOCTO_DOCS_GS_URL;#overview-checksums'>signatures</ulink>", + "<ulink url='&YOCTO_DOCS_OM_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 @@ -8610,7 +8610,7 @@ Some notes from Cal: <para> For more information on shared state, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#shared-state-cache'>Shared State Cache</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#shared-state-cache'>Shared State Cache</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> @@ -8856,7 +8856,7 @@ Some notes from Cal: <filename>connman.inc</filename> file in the <filename>meta/recipes-connectivity/connman/</filename> directory of the <filename>poky</filename> - <ulink url='&YOCTO_DOCS_GS_URL;#yocto-project-repositories'>source repository</ulink>. + <ulink url='&YOCTO_DOCS_OM_URL;#yocto-project-repositories'>source repository</ulink>. You can also find examples in <filename>meta/classes/kernel.bbclass</filename>. </para> @@ -10399,7 +10399,7 @@ Some notes from Cal: Enabling build history as previously described causes the OpenEmbedded build system to collect build output information and commit it as a single commit to a local - <ulink url='&YOCTO_DOCS_GS_URL;#git'>Git</ulink> + <ulink url='&YOCTO_DOCS_OM_URL;#git'>Git</ulink> repository. <note> Enabling build history increases your build times slightly, @@ -12261,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_GS_URL;#shared-state-cache'>sstate</ulink>) + (<ulink url='&YOCTO_DOCS_OM_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> @@ -12370,7 +12370,7 @@ 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_GS_URL;#stamp-files-and-the-rerunning-of-tasks'>Stamp Files and the Rerunning of Tasks</ulink>" + "<ulink url='&YOCTO_DOCS_OM_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> diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml index 1579a4e89e..6ccf21882b 100644 --- a/documentation/dev-manual/dev-manual-newbie.xml +++ b/documentation/dev-manual/dev-manual-newbie.xml @@ -99,7 +99,7 @@ with the OpenEmbedded build system is advisable. Of the SCMs BitBake supports, the Yocto Project team strongly recommends using - <ulink url='&YOCTO_DOCS_GS_URL;#git'>Git</ulink>. + <ulink url='&YOCTO_DOCS_OM_URL;#git'>Git</ulink>. Git is a distributed system that is easy to backup, allows you to work remotely, and then connects back to the infrastructure. @@ -311,7 +311,7 @@ <itemizedlist> <listitem><para> Use - <ulink url='&YOCTO_DOCS_GS_URL;#git'>Git</ulink> + <ulink url='&YOCTO_DOCS_OM_URL;#git'>Git</ulink> as the source control system. </para></listitem> <listitem><para> @@ -325,7 +325,7 @@ Separate the project's Metadata and code by using separate Git repositories. See the - "<ulink url='&YOCTO_DOCS_GS_URL;#yocto-project-repositories'>Yocto Project Source Repositories</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#yocto-project-repositories'>Yocto Project Source Repositories</ulink>" section for information on these repositories. See the "<link linkend='working-with-yocto-project-source-files'>Working With Yocto Project Source Files</link>" @@ -549,7 +549,7 @@ pull the change into the component's upstream repository. You do this by pushing to a contribution repository that is upstream. See the - "<ulink url='&YOCTO_DOCS_GS_URL;#gs-git-workflows-and-the-yocto-project'>Git Workflows and the Yocto Project</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#gs-git-workflows-and-the-yocto-project'>Git Workflows and the Yocto Project</ulink>" section in the Yocto Project Overview and Concepts Manual for additional concepts on working in the Yocto Project development environment. </para> @@ -749,7 +749,7 @@ </para></listitem> <listitem><para> <emphasis>Search by File:</emphasis> - Using <ulink url='&YOCTO_DOCS_GS_URL;#git'>Git</ulink>, + Using <ulink url='&YOCTO_DOCS_OM_URL;#git'>Git</ulink>, you can enter the following command to bring up a short list of all commits against a specific file: <literallayout class='monospaced'> diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml index f7f274bc8d..87d8757a09 100644 --- a/documentation/dev-manual/dev-manual-start.xml +++ b/documentation/dev-manual/dev-manual-start.xml @@ -260,12 +260,12 @@ <listitem><para> For concepts and introductory information about Git as it is used in the Yocto Project, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#git'>Git</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#git'>Git</ulink>" section in the Yocto Project Overview and Concepts Manual. </para></listitem> <listitem><para> For concepts on Yocto Project source repositories, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#yocto-project-repositories'>Yocto Project Source Repositories</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#yocto-project-repositories'>Yocto Project Source Repositories</ulink>" section in the Yocto Project Overview and Concepts Manual." </para></listitem> </itemizedlist> @@ -277,7 +277,7 @@ <para> Working from a copy of the upstream Yocto Project - <ulink url='&YOCTO_DOCS_GS_URL;#source-repositories'>Source Repositories</ulink> + <ulink url='&YOCTO_DOCS_OM_URL;#source-repositories'>Source Repositories</ulink> is the preferred method for obtaining and using a Yocto Project release. You can view the Yocto Project Source Repositories at @@ -306,7 +306,7 @@ <listitem><para> <emphasis>Find the URL Used to Clone the Repository:</emphasis> At the bottom of the page, note the URL used to - <ulink url='&YOCTO_DOCS_GS_URL;#git-commands-clone'>clone</ulink> + <ulink url='&YOCTO_DOCS_OM_URL;#git-commands-clone'>clone</ulink> that repository (e.g. <filename>&YOCTO_GIT_URL;/poky</filename>). <note> @@ -473,7 +473,7 @@ <para> You create your Source Directory by using - <ulink url='&YOCTO_DOCS_GS_URL;#git'>Git</ulink> to clone a local + <ulink url='&YOCTO_DOCS_OM_URL;#git'>Git</ulink> to clone a local copy of the upstream <filename>poky</filename> repository. <note><title>Tip</title> The preferred method of getting the Yocto Project Source @@ -748,7 +748,7 @@ <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_GS_URL;#images-dev-environment'>Images</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#images-dev-environment'>Images</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> diff --git a/documentation/kernel-dev/kernel-dev-advanced.xml b/documentation/kernel-dev/kernel-dev-advanced.xml index cf8d34dced..e152295233 100644 --- a/documentation/kernel-dev/kernel-dev-advanced.xml +++ b/documentation/kernel-dev/kernel-dev-advanced.xml @@ -21,7 +21,7 @@ <para> Kernel Metadata exists in many places. One area in the Yocto Project - <ulink url='&YOCTO_DOCS_GS_URL;#source-repositories'>Source Repositories</ulink> + <ulink url='&YOCTO_DOCS_OM_URL;#source-repositories'>Source Repositories</ulink> is the <filename>yocto-kernel-cache</filename> Git repository. You can find this repository grouped under the "Yocto Linux Kernel" heading in the diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml index d8eeb9ec50..6cc7b57ee7 100644 --- a/documentation/kernel-dev/kernel-dev-common.xml +++ b/documentation/kernel-dev/kernel-dev-common.xml @@ -79,7 +79,7 @@ </literallayout> <note> The previous commands assume the - <ulink url='&YOCTO_DOCS_GS_URL;#source-repositories'>Source Repositories</ulink> + <ulink url='&YOCTO_DOCS_OM_URL;#source-repositories'>Source Repositories</ulink> (i.e. <filename>poky</filename>) have been cloned using Git and the local repository is named "poky". @@ -303,7 +303,7 @@ </literallayout> <note> The previous commands assume the - <ulink url='&YOCTO_DOCS_GS_URL;#source-repositories'>Source Repositories</ulink> + <ulink url='&YOCTO_DOCS_OM_URL;#source-repositories'>Source Repositories</ulink> (i.e. <filename>poky</filename>) have been cloned using Git and the local repository is named "poky". diff --git a/documentation/kernel-dev/kernel-dev-concepts-appx.xml b/documentation/kernel-dev/kernel-dev-concepts-appx.xml index 46b5df0773..6d675a6d51 100644 --- a/documentation/kernel-dev/kernel-dev-concepts-appx.xml +++ b/documentation/kernel-dev/kernel-dev-concepts-appx.xml @@ -49,7 +49,7 @@ <para> You can find a web interface to the Yocto Linux kernels in the - <ulink url='&YOCTO_DOCS_GS_URL;#source-repositories'>Source Repositories</ulink> + <ulink url='&YOCTO_DOCS_OM_URL;#source-repositories'>Source Repositories</ulink> at <ulink url='&YOCTO_GIT_URL;'></ulink>. If you look at the interface, you will see to the left a @@ -239,7 +239,7 @@ <ulink url='http://git-scm.com/documentation'></ulink>. You can also get an introduction to Git as it applies to the Yocto Project in the - "<ulink url='&YOCTO_DOCS_GS_URL;#git'>Git</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#git'>Git</ulink>" section in the Yocto Project Overview and Concepts Manual. The latter reference provides an overview of @@ -382,7 +382,7 @@ generic kernel just for conceptual purposes. Also keep in mind that this structure represents the Yocto Project - <ulink url='&YOCTO_DOCS_GS_URL;#source-repositories'>Source Repositories</ulink> + <ulink url='&YOCTO_DOCS_OM_URL;#source-repositories'>Source Repositories</ulink> that are either pulled from during the build or established on the host development system prior to the build by either cloning a particular kernel's Git repository or by diff --git a/documentation/kernel-dev/kernel-dev-intro.xml b/documentation/kernel-dev/kernel-dev-intro.xml index ab087ce529..4e4fd282a5 100644 --- a/documentation/kernel-dev/kernel-dev-intro.xml +++ b/documentation/kernel-dev/kernel-dev-intro.xml @@ -112,7 +112,7 @@ document. </para></listitem> <listitem><para> - <ulink url='&YOCTO_DOCS_GS_URL;'>Yocto Project Overview and Concepts Manual</ulink>. + <ulink url='&YOCTO_DOCS_OM_URL;'>Yocto Project Overview and Concepts Manual</ulink>. </para></listitem> <listitem><para> <ulink url='&YOCTO_DOCS_SDK_URL;#using-devtool-in-your-sdk-workflow'><filename>devtool</filename> workflow</ulink> diff --git a/documentation/overview-manual/overview-manual-concepts.xml b/documentation/overview-manual/overview-manual-concepts.xml index 123cf15d19..5067e3f627 100644 --- a/documentation/overview-manual/overview-manual-concepts.xml +++ b/documentation/overview-manual/overview-manual-concepts.xml @@ -203,8 +203,8 @@ <para> For more introductory information on the Yocto Project's layer model, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#the-yocto-project-layer-model'>The Yocto Project Layer Model</ulink>" - section in the Yocto Project Overview and Concepts Manual. + "<link linkend='the-yocto-project-layer-model'>The Yocto Project Layer Model</link>" + section. For procedures on how to create layers, see the "<ulink url='&YOCTO_DOCS_DEV_URL;#understanding-and-creating-layers'>Understanding and Creating Layers</ulink>" section in the Yocto Project Development Tasks Manual. @@ -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_GS_URL;#overview-checksums'>input checksum</ulink>. + <link linkend='overview-checksums'>input checksum</link>. <note> This naming scheme assumes that <ulink url='&YOCTO_DOCS_BB_URL;#var-BB_SIGNATURE_HANDLER'><filename>BB_SIGNATURE_HANDLER</filename></ulink> diff --git a/documentation/overview-manual/overview-manual-yp-intro.xml b/documentation/overview-manual/overview-manual-yp-intro.xml index 437635842a..c38de74fd1 100644 --- a/documentation/overview-manual/overview-manual-yp-intro.xml +++ b/documentation/overview-manual/overview-manual-yp-intro.xml @@ -654,9 +654,8 @@ when they do not.</para> <para>You can read more about Pseudo in the - "<ulink url='&YOCTO_DOCS_GS_URL;#fakeroot-and-pseudo'>Fakeroot and Pseudo</ulink>" - section of the Yocto Project Overview and Concepts - Manual. + "<link linkend='fakeroot-and-pseudo'>Fakeroot and Pseudo</link>" + section. </para></listitem> </itemizedlist> </para> @@ -695,10 +694,8 @@ the Yocto Project. The Yocto Project and the OpenEmbedded Project both maintain the OpenEmbedded-Core. - You can find the OE-Core metadata in the Yocto - Project - <ulink url='&YOCTO_DOCS_GS_URL;#source-repositories'>Source Repositories</ulink> - <ulink url='https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta'>here</ulink>. + You can find the OE-Core metadata in the Yocto Project + <ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi/poky/tree/meta'>Source Repositories</ulink>. </para> <para>Historically, the Yocto Project integrated the @@ -777,9 +774,8 @@ in constrained environments.</para> <para>You can find the Matchbox source in its - <ulink url='http://git.yoctoproject.org/cgit/cgit.cgi'>repository</ulink> - listed in the Yocto Project - <ulink url='&YOCTO_DOCS_GS_URL;#source-repositories'>Source Repositories</ulink>. + <ulink url='&YOCTO_GIT_URL;/cgit/cgit.cgi'>repository</ulink> + listed in the Yocto Project Source Repositories. </para></listitem> <listitem><para> <emphasis>Opkg</emphasis> @@ -1143,8 +1139,8 @@ <para> For a very detailed look at this workflow, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#development-concepts'>Development Concepts</ulink>" - section in the Yocto Project Overview and Concepts Manual. + "<link linkend='development-concepts'>Development Concepts</link>" + section. </para> </section> diff --git a/documentation/ref-manual/faq.xml b/documentation/ref-manual/faq.xml index 770162c0ef..49ff86261d 100644 --- a/documentation/ref-manual/faq.xml +++ b/documentation/ref-manual/faq.xml @@ -417,7 +417,7 @@ <para> You can find more information on licensing in the - "<ulink url='&YOCTO_DOCS_GS_URL;#licensing'>Licensing</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#licensing'>Licensing</ulink>" section in the Yocto Project Overview and Concepts Manual and also in the "<ulink url='&YOCTO_DOCS_DEV_URL;#maintaining-open-source-license-compliance-during-your-products-lifecycle'>Maintaining Open Source License Compliance During Your Product's Lifecycle</ulink>" diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml index d8620eefd9..9a6aab95ab 100644 --- a/documentation/ref-manual/migration.xml +++ b/documentation/ref-manual/migration.xml @@ -293,7 +293,7 @@ For the remainder, you can now find them in the <filename>meta-extras</filename> repository, which is in the Yocto Project - <ulink url='&YOCTO_DOCS_GS_URL;#source-repositories'>Source Repositories</ulink>. + <ulink url='&YOCTO_DOCS_OM_URL;#source-repositories'>Source Repositories</ulink>. </para> </section> </section> @@ -1748,7 +1748,7 @@ <para> The minimum - <ulink url='&YOCTO_DOCS_GS_URL;#git'>Git</ulink> version + <ulink url='&YOCTO_DOCS_OM_URL;#git'>Git</ulink> version required on the build host is now 1.7.8 because the <filename>--list</filename> option is now required by BitBake's Git fetcher. @@ -4038,7 +4038,7 @@ $ runqemu qemux86-64 tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64. <para>For an example, see the <filename>pixbufcache</filename> class in <filename>meta/classes/</filename> in the Yocto Project - <ulink url='&YOCTO_DOCS_GS_URL;#source-repositories'>Source Repositories</ulink>. + <ulink url='&YOCTO_DOCS_OM_URL;#source-repositories'>Source Repositories</ulink>. <note> The <filename>SSTATEPOSTINSTFUNCS</filename> variable itself is now deprecated in favor of the diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml index e419e1321c..e432fd52aa 100644 --- a/documentation/ref-manual/ref-classes.xml +++ b/documentation/ref-manual/ref-classes.xml @@ -568,7 +568,7 @@ provides support for the recipes that build the Canadian Cross-compilation tools for SDKs. See the - "<ulink url='&YOCTO_DOCS_GS_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>" + "<ulink url='&YOCTO_DOCS_OM_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> @@ -582,7 +582,7 @@ provides support for the recipes that build the cross-compilation tools used for building SDKs. See the - "<ulink url='&YOCTO_DOCS_GS_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>" + "<ulink url='&YOCTO_DOCS_OM_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> @@ -1251,7 +1251,7 @@ "<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_GS_URL;#images-dev-environment'>Images</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#images-dev-environment'>Images</ulink>" section in the Yocto Project Overview and Concpets Manual. </para> </section> @@ -2722,7 +2722,7 @@ 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_GS_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>" + "<ulink url='&YOCTO_DOCS_OM_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 @@ -3020,7 +3020,7 @@ 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_GS_URL;#image-generation-dev-environment'>Image Generation</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#image-generation-dev-environment'>Image Generation</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> </section> @@ -3182,7 +3182,7 @@ This check was removed for YP 2.3 release <para> For more information on sstate, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#shared-state-cache'>Shared State Cache</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#shared-state-cache'>Shared State Cache</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> </section> diff --git a/documentation/ref-manual/ref-images.xml b/documentation/ref-manual/ref-images.xml index 0cfa5f3543..7f33eb649f 100644 --- a/documentation/ref-manual/ref-images.xml +++ b/documentation/ref-manual/ref-images.xml @@ -151,7 +151,7 @@ This image provides the Wayland protocol libraries and the reference Weston compositor. For more information, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#wayland'>Wayland</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#wayland'>Wayland</ulink>" section in the Yocto Project Overview and Concepts Manual. </para></listitem> <listitem><para><filename>core-image-x11</filename>: diff --git a/documentation/ref-manual/ref-release-process.xml b/documentation/ref-manual/ref-release-process.xml index d8ead1399b..c665cd938e 100644 --- a/documentation/ref-manual/ref-release-process.xml +++ b/documentation/ref-manual/ref-release-process.xml @@ -61,7 +61,7 @@ <para> Each major release receives a codename that identifies the release in the - <ulink url='&YOCTO_DOCS_GS_URL;#yocto-project-repositories'>Yocto Project Source Repositories</ulink>. + <ulink url='&YOCTO_DOCS_OM_URL;#yocto-project-repositories'>Yocto Project Source Repositories</ulink>. The concept is that branches of <link linkend='metadata'>Metadata</link> with the same codename are likely to be compatible and thus @@ -217,7 +217,7 @@ in the <filename>poky</filename> repository. <note> You can find all these branches in the Yocto Project - <ulink url='&YOCTO_DOCS_GS_URL;#source-repositories'>Source Repositories</ulink>. + <ulink url='&YOCTO_DOCS_OM_URL;#source-repositories'>Source Repositories</ulink>. </note> Testing within these public branches ensures in a publicly visible way that all of the main supposed architectures and recipes in OE-Core diff --git a/documentation/ref-manual/ref-structure.xml b/documentation/ref-manual/ref-structure.xml index 07f4e7c490..b42ea119d3 100644 --- a/documentation/ref-manual/ref-structure.xml +++ b/documentation/ref-manual/ref-structure.xml @@ -520,9 +520,9 @@ variable points to this directory. For more detail on the contents of the <filename>deploy</filename> directory, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#images-dev-environment'>Images</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#images-dev-environment'>Images</ulink>" and - "<ulink url='&YOCTO_DOCS_GS_URL;#sdk-dev-environment'>Application Development SDK</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#sdk-dev-environment'>Application Development SDK</ulink>" sections in the Yocto Project Overview and Concepts Manual. </para> </section> @@ -696,7 +696,7 @@ <para> For information on how BitBake uses stamp files to determine if a task should be rerun, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#stamp-files-and-the-rerunning-of-tasks'>Stamp Files and the Rerunning of Tasks</ulink>" + "<ulink url='&YOCTO_DOCS_OM_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> diff --git a/documentation/ref-manual/ref-system-requirements.xml b/documentation/ref-manual/ref-system-requirements.xml index cc6a172bf9..00d9678dbe 100644 --- a/documentation/ref-manual/ref-system-requirements.xml +++ b/documentation/ref-manual/ref-system-requirements.xml @@ -21,7 +21,7 @@ <para> For introductory information on the Yocto Project, see the <ulink url='&YOCTO_HOME_URL;'>Yocto Project Website</ulink> and the - "<ulink url='&YOCTO_DOCS_GS_URL;#overview-development-environment'>Yocto Project Development Environment</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#overview-development-environment'>Yocto Project Development Environment</ulink>" chapter in the Yocto Project Overview and Concepts Manual. </para> @@ -33,7 +33,7 @@ You can find "how-to" information in the <ulink url='&YOCTO_DOCS_DEV_URL;'>Yocto Project Development Tasks Manual</ulink>. You can find Yocto Project overview and conceptual information in the - <ulink url='&YOCTO_DOCS_GS_URL;'>Yocto Project Overview and Concepts Manual</ulink>. + <ulink url='&YOCTO_DOCS_OM_URL;'>Yocto Project Overview and Concepts Manual</ulink>. <note><title>Tip</title> For more information about the Yocto Project Documentation set, see the diff --git a/documentation/ref-manual/ref-tasks.xml b/documentation/ref-manual/ref-tasks.xml index 3226b17299..c551ff0f90 100644 --- a/documentation/ref-manual/ref-tasks.xml +++ b/documentation/ref-manual/ref-tasks.xml @@ -220,7 +220,7 @@ <para> For more information on image creation, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#image-generation-dev-environment'>Image Generation</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#image-generation-dev-environment'>Image Generation</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> </section> @@ -246,7 +246,7 @@ <para> For more information on image creation, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#image-generation-dev-environment'>Image Generation</ulink>" + "<ulink url='&YOCTO_DOCS_OM_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_GS_URL;#fakeroot-and-pseudo'>fakeroot</ulink>. + <ulink url='&YOCTO_DOCS_OM_URL;#fakeroot-and-pseudo'>fakeroot</ulink>. <note> <title>Caution</title> @@ -342,7 +342,7 @@ For additional information, see the <link linkend='var-PKGDESTWORK'><filename>PKGDESTWORK</filename></link> variable and the - "<ulink url='&YOCTO_DOCS_GS_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> </section> @@ -367,7 +367,7 @@ <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_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> </section> @@ -381,7 +381,7 @@ <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_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> </section> @@ -395,7 +395,7 @@ <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_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> </section> @@ -408,7 +408,7 @@ <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_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> </section> @@ -431,7 +431,7 @@ <para> Locates patch files and applies them to the source code. See the - "<ulink url='&YOCTO_DOCS_GS_URL;#patching-dev-environment'>Patching</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#patching-dev-environment'>Patching</ulink>" section in the Yocto Project Overview and Concepts Manual for more information. </para> @@ -452,7 +452,7 @@ <para> Creates the file and directory structure for an installable SDK. See the - "<ulink url='&YOCTO_DOCS_GS_URL;#sdk-generation-dev-environment'>SDK Generation</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#sdk-generation-dev-environment'>SDK Generation</ulink>" section in the Yocto Project Overview and Concepts Manual for more information. </para> @@ -540,7 +540,7 @@ <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_GS_URL;#source-fetching-dev-environment'>Source Fetching</ulink>" + "<ulink url='&YOCTO_DOCS_OM_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. @@ -620,7 +620,7 @@ <para> Running this task does not remove the - <ulink url='&YOCTO_DOCS_GS_URL;#shared-state-cache'>sstate</ulink> + <ulink url='&YOCTO_DOCS_OM_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_GS_URL;#shared-state-cache'>sstate</ulink>) + (<ulink url='&YOCTO_DOCS_OM_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_GS_URL;#shared-state-cache'>sstate</ulink>) + (<ulink url='&YOCTO_DOCS_OM_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_GS_URL;#shared-state-cache'>sstate</ulink>) + (<ulink url='&YOCTO_DOCS_OM_URL;#shared-state-cache'>sstate</ulink>) cache. </para> @@ -744,7 +744,7 @@ <para> Creates or updates the index in the - <ulink url='&YOCTO_DOCS_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink> + <ulink url='&YOCTO_DOCS_OM_URL;#package-feeds-dev-environment'>Package Feeds</ulink> area. <note> This task is not triggered with the @@ -796,7 +796,7 @@ Creates the root filesystem (file and directory structure) for an image. See the - "<ulink url='&YOCTO_DOCS_GS_URL;#image-generation-dev-environment'>Image Generation</ulink>" + "<ulink url='&YOCTO_DOCS_OM_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> diff --git a/documentation/ref-manual/ref-terms.xml b/documentation/ref-manual/ref-terms.xml index 31bcbe6e0b..a0c0371339 100644 --- a/documentation/ref-manual/ref-terms.xml +++ b/documentation/ref-manual/ref-terms.xml @@ -200,7 +200,7 @@ <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_GS_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>" + "<ulink url='&YOCTO_DOCS_OM_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 @@ -245,7 +245,7 @@ Yocto Project.</para> <para>For introductory information on layers, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#the-yocto-project-layer-model'>The Yocto Project Layer Model</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#the-yocto-project-layer-model'>The Yocto Project Layer Model</ulink>" section in the Yocto Project Overview and Concepts Manual. For more detailed information on layers, see the "<ulink url='&YOCTO_DOCS_DEV_URL;#understanding-and-creating-layers'>Understanding and Creating Layers</ulink>" @@ -470,7 +470,7 @@ <para>For more information on concepts related to Git repositories, branches, and tags, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#repositories-tags-and-branches'>Repositories, Tags, and Branches</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#repositories-tags-and-branches'>Repositories, Tags, and Branches</ulink>" section in the Yocto Project Overview and Concepts Manual. </para></listitem> <listitem><para><emphasis>Task:</emphasis> diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index 01bbc1c473..0287b910a0 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -3017,7 +3017,7 @@ <note><title>Caution</title> Tasks that read from or write to this directory should run under - <ulink url='&YOCTO_DOCS_GS_URL;#fakeroot-and-pseudo'>fakeroot</ulink>. + <ulink url='&YOCTO_DOCS_OM_URL;#fakeroot-and-pseudo'>fakeroot</ulink>. </note> </para> </glossdef> @@ -3264,7 +3264,7 @@ add any runtime dependencies between the packages produced by the two recipes. However, as explained in the - "<ulink url='&YOCTO_DOCS_GS_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>" + "<ulink url='&YOCTO_DOCS_OM_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 @@ -3329,10 +3329,10 @@ section. For more detail on the contents of the <filename>deploy</filename> directory, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#images-dev-environment'>Images</ulink>", - "<ulink url='&YOCTO_DOCS_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>", + "<ulink url='&YOCTO_DOCS_OM_URL;#images-dev-environment'>Images</ulink>", + "<ulink url='&YOCTO_DOCS_OM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>", and - "<ulink url='&YOCTO_DOCS_GS_URL;#sdk-dev-environment'>Application Development SDK</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#sdk-dev-environment'>Application Development SDK</ulink>" sections all in the Yocto Project Overview and Concepts Manual. </para> @@ -3373,7 +3373,7 @@ <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_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> </glossdef> @@ -3403,9 +3403,9 @@ section. For more detail on the contents of the <filename>deploy</filename> directory, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#images-dev-environment'>Images</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#images-dev-environment'>Images</ulink>" and - "<ulink url='&YOCTO_DOCS_GS_URL;#sdk-dev-environment'>Application Development SDK</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#sdk-dev-environment'>Application Development SDK</ulink>" sections both in the Yocto Project Overview and Concepts Manual. </para> @@ -3445,7 +3445,7 @@ <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_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> </glossdef> @@ -3484,7 +3484,7 @@ <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_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> </glossdef> @@ -3523,7 +3523,7 @@ <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_GS_URL;#package-feeds-dev-environment'>Package Feeds</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#package-feeds-dev-environment'>Package Feeds</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> </glossdef> @@ -4865,7 +4865,7 @@ The previous statement appears in the <filename>linux-yocto-dev.bbappend</filename> file, which is found in the Yocto Project - <ulink url='&YOCTO_DOCS_GS_URL;#source-repositories'>Source Repositories</ulink> + <ulink url='&YOCTO_DOCS_OM_URL;#source-repositories'>Source Repositories</ulink> in <filename>meta-intel/common/recipes-kernel/linux</filename>. Here, the machine override is a special @@ -6106,7 +6106,7 @@ variables. You can find information on how the image is created in the - "<ulink url='&YOCTO_DOCS_GS_URL;#image-generation-dev-environment'>Image Generation</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#image-generation-dev-environment'>Image Generation</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> </glossdef> @@ -7980,7 +7980,7 @@ 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_GS_URL;#usingpoky-configuring-LIC_FILES_CHKSUM'>Tracking License Changes</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#usingpoky-configuring-LIC_FILES_CHKSUM'>Tracking License Changes</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> </glossdef> @@ -8116,7 +8116,7 @@ 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_GS_URL;#enabling-commercially-licensed-recipes'>Enabling Commercially Licensed Recipes</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#enabling-commercially-licensed-recipes'>Enabling Commercially Licensed Recipes</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> </glossdef> @@ -8136,7 +8136,7 @@ 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_GS_URL;#enabling-commercially-licensed-recipes'>Enabling Commercially Licensed Recipes</ulink>" + <ulink url='&YOCTO_DOCS_OM_URL;#enabling-commercially-licensed-recipes'>Enabling Commercially Licensed Recipes</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> </glossdef> @@ -10490,7 +10490,7 @@ 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_GS_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>" + "<ulink url='&YOCTO_DOCS_OM_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>" @@ -10738,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_GS_URL;#overview-checksums'>input checksums</ulink> + <ulink url='&YOCTO_DOCS_OM_URL;#overview-checksums'>input checksums</ulink> along with the <link linkend='structure-build-tmp-stamps'>stamp</link> and - <ulink url='&YOCTO_DOCS_GS_URL;#shared-state-cache'>shared state cache</ulink> + <ulink url='&YOCTO_DOCS_OM_URL;#shared-state-cache'>shared state cache</ulink> mechanisms. </note> The <filename>PR</filename> variable primarily becomes @@ -11011,7 +11011,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" <para> For more information, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> </glossdef> @@ -11328,7 +11328,7 @@ 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_GS_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#automatically-added-runtime-dependencies'>Automatically Added Runtime Dependencies</ulink>" section in the Yocto Project Overview and Concepts Manual. </para> @@ -13848,7 +13848,7 @@ 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_GS_URL;#stamp-files-and-the-rerunning-of-tasks'>Stamp Files and the Rerunning of Tasks</ulink>" + "<ulink url='&YOCTO_DOCS_OM_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> @@ -15340,7 +15340,7 @@ 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_GS_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>" + "<ulink url='&YOCTO_DOCS_OM_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 @@ -15399,7 +15399,7 @@ 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_GS_URL;#cross-development-toolchain-generation'>Cross-Development Toolchain Generation</ulink>" + "<ulink url='&YOCTO_DOCS_OM_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 diff --git a/documentation/ref-manual/resources.xml b/documentation/ref-manual/resources.xml index 52c64d460e..8d9ca34d0a 100644 --- a/documentation/ref-manual/resources.xml +++ b/documentation/ref-manual/resources.xml @@ -168,7 +168,7 @@ </para></listitem> <listitem><para> <emphasis> - <ulink url='&YOCTO_DOCS_GS_URL;'>Yocto Project Overview and Concepts Manual</ulink>: + <ulink url='&YOCTO_DOCS_OM_URL;'>Yocto Project Overview and Concepts Manual</ulink>: </emphasis> This manual provides overview and conceptual information about the Yocto Project. @@ -216,7 +216,7 @@ </para></listitem> <listitem><para> <emphasis> - <ulink url='&YOCTO_DOCS_MM_URL;'>Yocto Project Reference Mega-Manual</ulink>: + <ulink url='&YOCTO_DOCS_MM_URL;'>Yocto Project Mega-Manual</ulink>: </emphasis> This manual is simply a single HTML file comprised of the bulk of the Yocto Project manuals. diff --git a/documentation/sdk-manual/sdk-appendix-obtain.xml b/documentation/sdk-manual/sdk-appendix-obtain.xml index ffdc3063b6..ac461e62dd 100644 --- a/documentation/sdk-manual/sdk-appendix-obtain.xml +++ b/documentation/sdk-manual/sdk-appendix-obtain.xml @@ -327,7 +327,7 @@ <para>Following is an example command that extracts the root filesystem from a previously built root filesystem image that was downloaded from the - <ulink url='&YOCTO_DOCS_GS_URL;#index-downloads'>Index of Releases</ulink>. + <ulink url='&YOCTO_DOCS_OM_URL;#index-downloads'>Index of Releases</ulink>. This command extracts the root filesystem into the <filename>core2-64-sato</filename> directory: <literallayout class='monospaced'> diff --git a/documentation/sdk-manual/sdk-extensible.xml b/documentation/sdk-manual/sdk-extensible.xml index 246b5eae84..4303054cba 100644 --- a/documentation/sdk-manual/sdk-extensible.xml +++ b/documentation/sdk-manual/sdk-extensible.xml @@ -247,7 +247,7 @@ <para> The <filename>devtool</filename> command line is organized similarly to - <ulink url='&YOCTO_DOCS_GS_URL;#git'>Git</ulink> in that it + <ulink url='&YOCTO_DOCS_OM_URL;#git'>Git</ulink> in that it has a number of sub-commands for each function. You can run <filename>devtool --help</filename> to see all the commands. diff --git a/documentation/toaster-manual/toaster-manual-reference.xml b/documentation/toaster-manual/toaster-manual-reference.xml index ae4e95a472..03ab35fc99 100644 --- a/documentation/toaster-manual/toaster-manual-reference.xml +++ b/documentation/toaster-manual/toaster-manual-reference.xml @@ -92,7 +92,7 @@ <para> For general information on layers, see the - "<ulink url='&YOCTO_DOCS_GS_URL;#the-yocto-project-layer-model'>The Yocto Project Layer Model</ulink>" + "<ulink url='&YOCTO_DOCS_OM_URL;#the-yocto-project-layer-model'>The Yocto Project Layer Model</ulink>" section in the Yocto Project Overview and Concepts Manual. For information on how to create layers, see the "<ulink url='&YOCTO_DOCS_DEV_URL;#understanding-and-creating-layers'>Understanding and Creating Layers</ulink>" |