From: "Nicolas Dechesne" <nicolas.dechesne@linaro.org>
To: docs@lists.yoctoproject.org
Cc: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Subject: [PATCH 04/11] dev-manual: replace labels with references to section title
Date: Thu, 19 Nov 2020 10:58:27 +0100 [thread overview]
Message-ID: <20201119095834.284864-5-nicolas.dechesne@linaro.org> (raw)
In-Reply-To: <20201119095834.284864-1-nicolas.dechesne@linaro.org>
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
---
.../dev-manual/dev-manual-common-tasks.rst | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/documentation/dev-manual/dev-manual-common-tasks.rst b/documentation/dev-manual/dev-manual-common-tasks.rst
index 27aacde60..201e187c3 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.rst
+++ b/documentation/dev-manual/dev-manual-common-tasks.rst
@@ -1143,7 +1143,7 @@ necessary when adding a recipe to build a new piece of software to be
included in a build.
You can find a complete description of the ``devtool add`` command in
-the ":ref:`sdk-a-closer-look-at-devtool-add`" section
+the ":ref:`sdk-manual/sdk-extensible:a closer look at \`\`devtool add\`\``" section
in the Yocto Project Application Development and the Extensible Software
Development Kit (eSDK) manual.
@@ -1819,7 +1819,7 @@ Here are some common issues that cause failures.
For cases where improper paths are detected for configuration files
or for when libraries/headers cannot be found, be sure you are using
the more robust ``pkg-config``. See the note in section
- ":ref:`new-recipe-configuring-the-recipe`" for additional information.
+ ":ref:`dev-manual/dev-manual-common-tasks:Configuring the Recipe`" for additional information.
- *Parallel build failures:* These failures manifest themselves as
intermittent errors, or errors reporting that a file or directory
@@ -3048,7 +3048,7 @@ The following steps describe how to set up the AUH utility:
1. *Be Sure the Development Host is Set Up:* You need to be sure that
your development host is set up to use the Yocto Project. For
information on how to set up your host, see the
- ":ref:`dev-preparing-the-build-host`" section.
+ ":ref:`dev-manual/dev-manual-start:Preparing the Build Host`" section.
2. *Make Sure Git is Configured:* The AUH utility requires Git to be
configured because AUH uses Git to save upgrades. Thus, you must have
@@ -3216,7 +3216,7 @@ As mentioned earlier, an alternative method for upgrading recipes to
newer versions is to use
:doc:`devtool upgrade <../ref-manual/ref-devtool-reference>`.
You can read about ``devtool upgrade`` in general in the
-":ref:`sdk-devtool-use-devtool-upgrade-to-create-a-version-of-the-recipe-that-supports-a-newer-version-of-the-software`"
+":ref:`sdk-manual/sdk-extensible:use \`\`devtool upgrade\`\` to create a version of the recipe that supports a newer version of the software`"
section in the Yocto Project Application Development and the Extensible
Software Development Kit (eSDK) Manual.
@@ -3356,7 +3356,8 @@ Manually Upgrading a Recipe
---------------------------
If for some reason you choose not to upgrade recipes using
-:ref:`gs-using-the-auto-upgrade-helper` or by :ref:`gs-using-devtool-upgrade`,
+:ref:`dev-manual/dev-manual-common-tasks:Using the Auto Upgrade Helper (AUH)` or
+by :ref:`dev-manual/dev-manual-common-tasks:Using \`\`devtool upgrade\`\``,
you can manually edit the recipe files to upgrade the versions.
.. note::
@@ -4196,7 +4197,7 @@ view file dependencies in a human-readable form:
directory.
For more information on configuration fragments, see the
- ":ref:`creating-config-fragments`"
+ ":ref:`kernel-dev/kernel-dev-common:creating configuration fragments`"
section in the Yocto Project Linux Kernel Development Manual.
- ``bitbake -u taskexp -g bitbake_target``: Using the BitBake command
@@ -8143,7 +8144,7 @@ associated ``EXTRA_IMAGE_FEATURES`` variable, as in:
EXTRA_IMAGE_FEATURES = "read-only-rootfs"
For more information on how to use these variables, see the
-":ref:`usingpoky-extend-customimage-imagefeatures`"
+":ref:`dev-manual/dev-manual-common-tasks:Customizing Images Using Custom \`\`IMAGE_FEATURES\`\` and \`\`EXTRA_IMAGE_FEATURES\`\``"
section. For information on the variables, see
:term:`IMAGE_FEATURES` and
:term:`EXTRA_IMAGE_FEATURES`.
--
2.29.2
next prev parent reply other threads:[~2020-11-19 9:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 9:58 [PATCH 00/11] A first pass at removing labels Nicolas Dechesne
2020-11-19 9:58 ` [PATCH 01/11] what-i-wish-id-known: replace labels with references to section title Nicolas Dechesne
2020-11-19 9:58 ` [PATCH 02/11] sdk-manual: " Nicolas Dechesne
2020-11-19 9:58 ` [PATCH 03/11] ref-manual: " Nicolas Dechesne
2020-11-19 9:58 ` Nicolas Dechesne [this message]
2020-11-19 9:58 ` [PATCH 05/11] kernel-dev: " Nicolas Dechesne
2020-11-19 9:58 ` [PATCH 06/11] test-manual: remove unused labels Nicolas Dechesne
2020-11-19 9:58 ` [PATCH 07/11] bsp-guide: " Nicolas Dechesne
2020-11-19 9:58 ` [PATCH 08/11] kernel-dev: " Nicolas Dechesne
2020-11-19 9:58 ` [PATCH 09/11] profile-manual: " Nicolas Dechesne
2020-11-19 9:58 ` [PATCH 10/11] sdk-manual: " Nicolas Dechesne
2020-11-19 9:58 ` [PATCH 11/11] toaster-manual: " Nicolas Dechesne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201119095834.284864-5-nicolas.dechesne@linaro.org \
--to=nicolas.dechesne@linaro.org \
--cc=docs@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.