* [PATCH 0/7] A second pass at removing labels
@ 2020-11-26 9:48 Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 1/7] sphinx: replace bitbake labels with references to corresponding title Nicolas Dechesne
` (6 more replies)
0 siblings, 7 replies; 8+ messages in thread
From: Nicolas Dechesne @ 2020-11-26 9:48 UTC (permalink / raw)
To: docs; +Cc: Nicolas Dechesne
This is a followup series similar to:
https://lists.yoctoproject.org/g/docs/message/659
I have now removed all labels from dev-manual and overview-manual. I
am also preparing the removal of labels in the bitbake manual, I will
send the patches when this series is merged.
The only manual that still has labels is ref-manual, but there the
labels are heavily used.. and many section titles use backquotes, so I
will wait to see what we do with that. If we remove them, i think it's
better to do that first, then remove the labels.
Nicolas Dechesne (7):
sphinx: replace bitbake labels with references to corresponding title
brief-yoctoprojectqs: replace labels with references to section title
dev-manual: replace labels with references to section title
ref-manual: replace labels with references to section title
sdk-manual: replace labels with references to section title
overview-manual: remove unused labels
dev-manual: remove unused labels
.../brief-yoctoprojectqs.rst | 4 +-
.../dev-manual/dev-manual-common-tasks.rst | 245 +-----------------
documentation/dev-manual/dev-manual-intro.rst | 2 -
documentation/dev-manual/dev-manual-qemu.rst | 14 -
documentation/dev-manual/dev-manual-start.rst | 10 -
.../kernel-dev/kernel-dev-advanced.rst | 2 +-
.../overview-manual-concepts.rst | 46 +---
...verview-manual-development-environment.rst | 6 -
.../overview-manual/overview-manual-intro.rst | 4 -
.../overview-manual-yp-intro.rst | 22 --
documentation/ref-manual/migration-2.3.rst | 2 +-
documentation/ref-manual/migration-2.6.rst | 2 +-
documentation/ref-manual/ref-classes.rst | 16 +-
.../ref-manual/ref-devtool-reference.rst | 6 +-
documentation/ref-manual/ref-features.rst | 2 +-
documentation/ref-manual/ref-structure.rst | 6 +-
documentation/ref-manual/ref-tasks.rst | 32 +--
documentation/ref-manual/ref-variables.rst | 78 +++---
documentation/ref-manual/resources.rst | 2 +-
.../sdk-manual/sdk-appendix-obtain.rst | 2 +-
documentation/sdk-manual/sdk-extensible.rst | 2 +-
21 files changed, 94 insertions(+), 411 deletions(-)
--
2.29.2
^ permalink raw reply [flat|nested] 8+ messages in thread
* [PATCH 1/7] sphinx: replace bitbake labels with references to corresponding title
2020-11-26 9:48 [PATCH 0/7] A second pass at removing labels Nicolas Dechesne
@ 2020-11-26 9:48 ` Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 2/7] brief-yoctoprojectqs: replace labels with references to section title Nicolas Dechesne
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Nicolas Dechesne @ 2020-11-26 9:48 UTC (permalink / raw)
To: docs; +Cc: Nicolas Dechesne
In order to remove autogenerated labels in the bibtake docs, let's use
section titles in all YP docs.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
---
documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.rst | 2 +-
documentation/dev-manual/dev-manual-common-tasks.rst | 4 ++--
documentation/kernel-dev/kernel-dev-advanced.rst | 2 +-
documentation/overview-manual/overview-manual-concepts.rst | 6 +++---
documentation/ref-manual/migration-2.3.rst | 2 +-
documentation/ref-manual/migration-2.6.rst | 2 +-
documentation/ref-manual/ref-devtool-reference.rst | 2 +-
documentation/ref-manual/ref-tasks.rst | 2 +-
documentation/ref-manual/ref-variables.rst | 4 ++--
documentation/sdk-manual/sdk-extensible.rst | 2 +-
10 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.rst b/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.rst
index c9622d364..f8c3ad974 100644
--- a/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.rst
+++ b/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.rst
@@ -246,7 +246,7 @@ an entire Linux distribution, including the toolchain, from source.
For information on using the ``bitbake`` command, see the
:ref:`usingpoky-components-bitbake` section in the Yocto Project Overview and
Concepts Manual, or see the ":ref:`BitBake Command
- <bitbake:bitbake-user-manual-command>`" section in the BitBake User Manual.
+ <bitbake:bitbake-user-manual/bitbake-user-manual-intro:the bitbake command>`" section in the BitBake User Manual.
#. **Simulate Your Image Using QEMU:** Once this particular image is
built, you can start QEMU, which is a Quick EMUlator that ships with
diff --git a/documentation/dev-manual/dev-manual-common-tasks.rst b/documentation/dev-manual/dev-manual-common-tasks.rst
index 683f5557e..1640a884d 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.rst
+++ b/documentation/dev-manual/dev-manual-common-tasks.rst
@@ -1369,7 +1369,7 @@ the Yocto Project Overview and Concepts Manual.
The :ref:`ref-tasks-fetch` task uses
the prefix of each entry in the ``SRC_URI`` variable value to determine
-which :ref:`fetcher <bitbake:bb-fetchers>` to use to get your
+which :ref:`fetcher <bitbake:bitbake-user-manual/bitbake-user-manual-fetching:fetchers>` to use to get your
source files. It is the ``SRC_URI`` variable that triggers the fetcher.
The :ref:`ref-tasks-patch` task uses
the variable after source is fetched to apply patches. The OpenEmbedded
@@ -7567,7 +7567,7 @@ Creating Node Package Manager (NPM) Packages
`NPM <https://en.wikipedia.org/wiki/Npm_(software)>`__ is a package
manager for the JavaScript programming language. The Yocto Project
-supports the NPM :ref:`fetcher <bitbake:bb-fetchers>`. You can
+supports the NPM :ref:`fetcher <bitbake:bitbake-user-manual/bitbake-user-manual-fetching:fetchers>`. You can
use this fetcher in combination with
:doc:`devtool <../ref-manual/ref-devtool-reference>` to create
recipes that produce NPM packages.
diff --git a/documentation/kernel-dev/kernel-dev-advanced.rst b/documentation/kernel-dev/kernel-dev-advanced.rst
index ca049316e..6999057b8 100644
--- a/documentation/kernel-dev/kernel-dev-advanced.rst
+++ b/documentation/kernel-dev/kernel-dev-advanced.rst
@@ -369,7 +369,7 @@ in the "`Features <#features>`__" section. The
variable in the kernel recipe selects the kernel type. For example, in
the ``linux-yocto_4.12.bb`` kernel recipe found in
``poky/meta/recipes-kernel/linux``, a
-:ref:`require <bitbake:require-inclusion>` directive
+:ref:`require <bitbake:bitbake-user-manual/bitbake-user-manual-metadata:\`\`require\`\` directive>` directive
includes the ``poky/meta/recipes-kernel/linux/linux-yocto.inc`` file,
which has the following statement that defines the default kernel type:
::
diff --git a/documentation/overview-manual/overview-manual-concepts.rst b/documentation/overview-manual/overview-manual-concepts.rst
index 736fd9591..f1f2b7f35 100644
--- a/documentation/overview-manual/overview-manual-concepts.rst
+++ b/documentation/overview-manual/overview-manual-concepts.rst
@@ -78,7 +78,7 @@ versions of ``matchbox-desktop`` might exist. BitBake chooses the one
selected by the distribution configuration. You can get more details
about how BitBake chooses between different target versions and
providers in the
-":ref:`Preferences <bitbake:bb-bitbake-preferences>`" section
+":ref:`Preferences <bitbake:bitbake-user-manual/bitbake-user-manual-execution:preferences>`" section
of the BitBake User Manual.
BitBake also tries to execute any dependent tasks first. So for example,
@@ -607,7 +607,7 @@ Source Control Managers (Optional)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Another place from which the build system can get source files is with
-:ref:`fetchers <bitbake:bb-fetchers>` employing various Source
+:ref:`fetchers <bitbake:bitbake-user-manual/bitbake-user-manual-fetching:fetchers>` employing various Source
Control Managers (SCMs) such as Git or Subversion. In such cases, a
repository is cloned or checked out. The
:ref:`ref-tasks-fetch` task inside
@@ -1949,7 +1949,7 @@ The following list explains the previous example:
extra metadata to the `stamp
file <#stamp-files-and-the-rerunning-of-tasks>`__. In this case, the
metadata makes the task specific to a machine's architecture. See
- ":ref:`bitbake:ref-bitbake-tasklist`"
+ ":ref:`bitbake:bitbake-user-manual/bitbake-user-manual-execution:the task list`"
section in the BitBake User Manual for more information on the
``stamp-extra-info`` flag.
diff --git a/documentation/ref-manual/migration-2.3.rst b/documentation/ref-manual/migration-2.3.rst
index 5bf3e7033..4041ad055 100644
--- a/documentation/ref-manual/migration-2.3.rst
+++ b/documentation/ref-manual/migration-2.3.rst
@@ -198,7 +198,7 @@ The following changes took place for BitBake:
fetcher passes the new parameter through the ``SVN_SSH`` environment
variable during the :ref:`ref-tasks-fetch` task.
- See the ":ref:`bitbake:svn-fetcher`"
+ See the ":ref:`bitbake:bitbake-user-manual/bitbake-user-manual-fetching:subversion (svn) fetcher (\`\`svn://\`\`)`"
section in the BitBake
User Manual for additional information.
diff --git a/documentation/ref-manual/migration-2.6.rst b/documentation/ref-manual/migration-2.6.rst
index 2f0da48ab..cc7c24c5b 100644
--- a/documentation/ref-manual/migration-2.6.rst
+++ b/documentation/ref-manual/migration-2.6.rst
@@ -278,7 +278,7 @@ The following changes have occurred:
specifying list items to remove, be aware that leading and trailing
whitespace resulting from the removal is retained.
- See the ":ref:`bitbake:removing-override-style-syntax`"
+ See the ":ref:`bitbake:bitbake-user-manual/bitbake-user-manual-metadata:removal (override style syntax)`"
section in the BitBake User Manual for a detailed example.
.. _migration-2.6-systemd-configuration-now-split-out-to-system-conf:
diff --git a/documentation/ref-manual/ref-devtool-reference.rst b/documentation/ref-manual/ref-devtool-reference.rst
index ad8889ed2..3f95f8d70 100644
--- a/documentation/ref-manual/ref-devtool-reference.rst
+++ b/documentation/ref-manual/ref-devtool-reference.rst
@@ -352,7 +352,7 @@ particular recipe.
`maintainers.inc <http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc>`_
file.
- - If the recipe is using the :ref:`bitbake:git-fetcher`
+ - If the recipe is using the :ref:`bitbake:bitbake-user-manual/bitbake-user-manual-fetching:git fetcher (\`\`git://\`\`)`
rather than a
tarball, the commit hash points to the commit that matches the
recipe's latest version tag.
diff --git a/documentation/ref-manual/ref-tasks.rst b/documentation/ref-manual/ref-tasks.rst
index 9ef014139..88b285d76 100644
--- a/documentation/ref-manual/ref-tasks.rst
+++ b/documentation/ref-manual/ref-tasks.rst
@@ -122,7 +122,7 @@ If the ``do_deploy`` task re-executes, any previous output is removed
Fetches the source code. This task uses the
:term:`SRC_URI` variable and the argument's prefix to
-determine the correct :ref:`fetcher <bitbake:bb-fetchers>`
+determine the correct :ref:`fetcher <bitbake:bitbake-user-manual/bitbake-user-manual-fetching:fetchers>`
module.
.. _ref-tasks-image:
diff --git a/documentation/ref-manual/ref-variables.rst b/documentation/ref-manual/ref-variables.rst
index e552351e3..56aeb583a 100644
--- a/documentation/ref-manual/ref-variables.rst
+++ b/documentation/ref-manual/ref-variables.rst
@@ -3062,7 +3062,7 @@ system and gives an overview of their function and contents.
section in the Yocto Project Development Tasks Manual.
- Using ``IMAGE_INSTALL`` with the
- :ref:`+= <bitbake:appending-and-prepending>`
+ :ref:`+= <bitbake:bitbake-user-manual/bitbake-user-manual-metadata:appending (+=) and prepending (=+) with spaces>`
BitBake operator within the ``/conf/local.conf`` file or from
within an image recipe is not recommended. Use of this operator
in these ways can cause ordering issues. Since
@@ -7018,7 +7018,7 @@ system and gives an overview of their function and contents.
protocols are highly dependent on particular BitBake Fetcher
submodules. Depending on the fetcher BitBake uses, various URL
parameters are employed. For specifics on the supported Fetchers, see
- the ":ref:`Fetchers <bitbake:bb-fetchers>`" section in the
+ the ":ref:`Fetchers <bitbake:bitbake-user-manual/bitbake-user-manual-fetching:fetchers>`" section in the
BitBake User Manual.
- ``file://`` - Fetches files, which are usually files shipped
diff --git a/documentation/sdk-manual/sdk-extensible.rst b/documentation/sdk-manual/sdk-extensible.rst
index 1a17da4f6..14ad23ba8 100644
--- a/documentation/sdk-manual/sdk-extensible.rst
+++ b/documentation/sdk-manual/sdk-extensible.rst
@@ -627,7 +627,7 @@ specify source code revision and versioning schemes, extract code into
or out of the ``devtool``
:ref:`devtool-the-workspace-layer-structure`,
and work with any source file forms that the
-:ref:`fetchers <bitbake:bb-fetchers>` support.
+:ref:`fetchers <bitbake:bitbake-user-manual/bitbake-user-manual-fetching:fetchers>` support.
The following diagram shows the common development flow used with the
``devtool upgrade`` command:
--
2.29.2
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH 2/7] brief-yoctoprojectqs: replace labels with references to section title
2020-11-26 9:48 [PATCH 0/7] A second pass at removing labels Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 1/7] sphinx: replace bitbake labels with references to corresponding title Nicolas Dechesne
@ 2020-11-26 9:48 ` Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 3/7] dev-manual: " Nicolas Dechesne
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Nicolas Dechesne @ 2020-11-26 9:48 UTC (permalink / raw)
To: docs; +Cc: Nicolas Dechesne
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
---
documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.rst b/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.rst
index f8c3ad974..f6d863f5b 100644
--- a/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.rst
+++ b/documentation/brief-yoctoprojectqs/brief-yoctoprojectqs.rst
@@ -244,7 +244,7 @@ an entire Linux distribution, including the toolchain, from source.
$ bitbake core-image-sato
For information on using the ``bitbake`` command, see the
- :ref:`usingpoky-components-bitbake` section in the Yocto Project Overview and
+ :ref:`overview-manual/overview-manual-concepts:bitbake` section in the Yocto Project Overview and
Concepts Manual, or see the ":ref:`BitBake Command
<bitbake:bitbake-user-manual/bitbake-user-manual-intro:the bitbake command>`" section in the BitBake User Manual.
--
2.29.2
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH 3/7] dev-manual: replace labels with references to section title
2020-11-26 9:48 [PATCH 0/7] A second pass at removing labels Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 1/7] sphinx: replace bitbake labels with references to corresponding title Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 2/7] brief-yoctoprojectqs: replace labels with references to section title Nicolas Dechesne
@ 2020-11-26 9:48 ` Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 4/7] ref-manual: " Nicolas Dechesne
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Nicolas Dechesne @ 2020-11-26 9:48 UTC (permalink / raw)
To: docs; +Cc: Nicolas Dechesne
---
.../dev-manual/dev-manual-common-tasks.rst | 21 ++++++++++---------
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/documentation/dev-manual/dev-manual-common-tasks.rst b/documentation/dev-manual/dev-manual-common-tasks.rst
index 1640a884d..23c2be4f4 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.rst
+++ b/documentation/dev-manual/dev-manual-common-tasks.rst
@@ -1364,7 +1364,7 @@ files. Fetching is controlled mainly through the
:term:`SRC_URI` variable. Your recipe
must have a ``SRC_URI`` variable that points to where the source is
located. For a graphical representation of source locations, see the
-":ref:`sources-dev-environment`" section in
+":ref:`overview-manual/overview-manual-concepts:sources`" section in
the Yocto Project Overview and Concepts Manual.
The :ref:`ref-tasks-fetch` task uses
@@ -3759,7 +3759,7 @@ build host running Linux.
The build process creates an entire Linux distribution from source and
places it in your :term:`Build Directory` under
``tmp/deploy/images``. For detailed information on the build process
-using BitBake, see the ":ref:`images-dev-environment`" section in the
+using BitBake, see the ":ref:`overview-manual/overview-manual-concepts:images`" section in the
Yocto Project Overview and Concepts Manual.
The following figure and list overviews the build process:
@@ -6663,7 +6663,7 @@ revision, respectively). The values are highly dependent on the policies
and procedures of a given distribution and package feed.
Because the OpenEmbedded build system uses
-":ref:`signatures <overview-checksums>`", which are
+":ref:`signatures <overview-manual/overview-manual-concepts:checksums (signatures)>`", 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
signature, which can trigger a rebuild when different. Thus, the build
@@ -6906,7 +6906,7 @@ multiple times if you have more than one set of modules to package.
For more examples that show how to use ``do_split_packages``, see the
``connman.inc`` file in the ``meta/recipes-connectivity/connman/``
-directory of the ``poky`` :ref:`source repository <yocto-project-repositories>`. You can
+directory of the ``poky`` :ref:`source repository <overview-manual/overview-manual-development-environment:yocto project source repositories>`. You can
also find examples in ``meta/classes/kernel.bbclass``.
Following is a reference that shows ``do_split_packages`` mandatory and
@@ -9661,7 +9661,7 @@ Invalidating Shared State to Force a Task to Run
------------------------------------------------
The OpenEmbedded build system uses
-:ref:`checksums <overview-checksums>` and
+:ref:`checksums <overview-manual/overview-manual-concepts:checksums (signatures)>` and
:ref:`overview-manual/overview-manual-concepts:shared state` cache to avoid unnecessarily
rebuilding tasks. Collectively, this scheme is known as "shared state
code".
@@ -10662,7 +10662,8 @@ Yocto general mailing list or on the openembedded-devel mailing list.
You can also push a change upstream and request a maintainer to pull the
change into the component's upstream repository. You do this by pushing
-to a contribution repository that is upstream. See the ":ref:`gs-git-workflows-and-the-yocto-project`"
+to a contribution repository that is upstream. See the
+":ref:`overview-manual/overview-manual-development-environment:git workflows and the yocto project`"
section in the Yocto Project Overview and Concepts Manual for additional
concepts on working in the Yocto Project development environment.
@@ -10789,7 +10790,7 @@ Yocto Project Reference Manual.
Here is the general procedure on how to submit a patch through email
without using the scripts once the steps in
-:ref:`preparing-changes-for-submissions` have been followed:
+:ref:`dev-manual/dev-manual-common-tasks:preparing changes for submission` have been followed:
1. *Format the Commit:* Format the commit into an email message. To
format commits, use the ``git format-patch`` command. When you
@@ -10880,7 +10881,7 @@ and ``send-pull-request`` scripts from openembedded-core to create and send a
patch series with a link to the branch for review.
Follow this procedure to push a change to an upstream "contrib" Git
-repository once the steps in :ref:`preparing-changes-for-submissions` have
+repository once the steps in :ref:`dev-manual/dev-manual-common-tasks:preparing changes for submission` have
been followed:
.. note::
@@ -11055,8 +11056,8 @@ follows:
a newer version of the software which includes an upstream fix for the
issue or when the issue has been fixed on the master branch in a way
that introduces backwards incompatible changes. In this case follow the
- steps in :ref:`preparing-changes-for-submissions` and
- :ref:`submitting-a-patch` but modify the subject header of your patch
+ steps in :ref:`dev-manual/dev-manual-common-tasks:preparing changes for submission` and
+ :ref:`dev-manual/dev-manual-common-tasks:using email to submit a patch` but modify the subject header of your patch
email to include the name of the stable branch which you are
targetting. This can be done using the ``--subject-prefix`` argument to
``git format-patch``, for example to submit a patch to the dunfell
--
2.29.2
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH 4/7] ref-manual: replace labels with references to section title
2020-11-26 9:48 [PATCH 0/7] A second pass at removing labels Nicolas Dechesne
` (2 preceding siblings ...)
2020-11-26 9:48 ` [PATCH 3/7] dev-manual: " Nicolas Dechesne
@ 2020-11-26 9:48 ` Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 5/7] sdk-manual: " Nicolas Dechesne
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Nicolas Dechesne @ 2020-11-26 9:48 UTC (permalink / raw)
To: docs; +Cc: Nicolas Dechesne
---
documentation/ref-manual/ref-classes.rst | 16 ++--
.../ref-manual/ref-devtool-reference.rst | 4 +-
documentation/ref-manual/ref-features.rst | 2 +-
documentation/ref-manual/ref-structure.rst | 6 +-
documentation/ref-manual/ref-tasks.rst | 30 ++++----
documentation/ref-manual/ref-variables.rst | 74 +++++++++----------
documentation/ref-manual/resources.rst | 2 +-
7 files changed, 67 insertions(+), 67 deletions(-)
diff --git a/documentation/ref-manual/ref-classes.rst b/documentation/ref-manual/ref-classes.rst
index 249b58e60..62876194d 100644
--- a/documentation/ref-manual/ref-classes.rst
+++ b/documentation/ref-manual/ref-classes.rst
@@ -86,7 +86,7 @@ standardization. This class defines a set of tasks (e.g. ``configure``,
should usually be enough to define a few standard variables and then
simply ``inherit autotools``. These classes can also work with software
that emulates Autotools. For more information, see the
-":ref:`new-recipe-autotooled-package`" section
+":ref:`dev-manual/dev-manual-common-tasks:autotooled package`" section
in the Yocto Project Development Tasks Manual.
By default, the ``autotools*`` classes use out-of-tree builds (i.e.
@@ -458,7 +458,7 @@ staging the files from ``DEPLOYDIR`` to ``DEPLOY_DIR_IMAGE``.
====================
The ``devshell`` class adds the ``do_devshell`` task. Distribution
-policy dictates whether to include this class. See the ":ref:`platdev-appdev-devshell`"
+policy dictates whether to include this class. See the ":ref:`dev-manual/dev-manual-common-tasks:using a development shell`"
section in the Yocto Project Development Tasks Manual for more
information about using ``devshell``.
@@ -927,10 +927,10 @@ then one or more image files are created.
install into the image.
For information on customizing images, see the
-":ref:`usingpoky-extend-customimage`" section
+":ref:`dev-manual/dev-manual-common-tasks:customizing images`" section
in the Yocto Project Development Tasks Manual. For information on how
images are created, see the
-":ref:`images-dev-environment`" section in the
+":ref:`overview-manual/overview-manual-concepts:images`" section in the
Yocto Project Overview and Concpets Manual.
.. _ref-classes-image-buildinfo:
@@ -1344,7 +1344,7 @@ packages such as ``kernel-vmlinux``.
The ``kernel`` class contains logic that allows you to embed an initial
RAM filesystem (initramfs) image when you build the kernel image. For
information on how to build an initramfs, see the
-":ref:`building-an-initramfs-image`" section in
+":ref:`dev-manual/dev-manual-common-tasks:building an initial ram filesystem (initramfs) image`" section in
the Yocto Project Development Tasks Manual.
Various other classes are used by the ``kernel`` and ``module`` classes
@@ -1620,7 +1620,7 @@ different target optimizations or target architectures and installing
them side-by-side in the same image.
For more information on using the Multilib feature, see the
-":ref:`combining-multiple-versions-library-files-into-one-image`"
+":ref:`dev-manual/dev-manual-common-tasks:combining multiple versions of library files into one image`"
section in the Yocto Project Development Tasks Manual.
.. _ref-classes-native:
@@ -1921,7 +1921,7 @@ so forth). It is highly recommended that all package group recipes
inherit this class.
For information on how to use this class, see the
-":ref:`usingpoky-extend-customimage-customtasks`"
+":ref:`dev-manual/dev-manual-common-tasks:customizing images using custom package groups`"
section in the Yocto Project Development Tasks Manual.
Previously, this class was called the ``task`` class.
@@ -2268,7 +2268,7 @@ The root filesystem is created from packages using one of the
:term:`PACKAGE_CLASSES` variable.
For information on how root filesystem images are created, see the
-":ref:`image-generation-dev-environment`"
+":ref:`overview-manual/overview-manual-concepts:image generation`"
section in the Yocto Project Overview and Concepts Manual.
.. _ref-classes-sanity:
diff --git a/documentation/ref-manual/ref-devtool-reference.rst b/documentation/ref-manual/ref-devtool-reference.rst
index 3f95f8d70..93fd1465f 100644
--- a/documentation/ref-manual/ref-devtool-reference.rst
+++ b/documentation/ref-manual/ref-devtool-reference.rst
@@ -413,7 +413,7 @@ Upgrading a Recipe
As software matures, upstream recipes are upgraded to newer versions. As
a developer, you need to keep your local recipes up-to-date with the
upstream version releases. Several methods exist by which you can
-upgrade recipes. You can read about them in the ":ref:`gs-upgrading-recipes`"
+upgrade recipes. You can read about them in the ":ref:`dev-manual/dev-manual-common-tasks:upgrading recipes`"
section of the Yocto Project Development Tasks Manual. This section
overviews the ``devtool upgrade`` command.
@@ -441,7 +441,7 @@ You can read more on the ``devtool upgrade`` workflow in the
":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. You can also see an example of
-how to use ``devtool upgrade`` in the ":ref:`gs-using-devtool-upgrade`"
+how to use ``devtool upgrade`` in the ":ref:`dev-manual/dev-manual-common-tasks:using \`\`devtool upgrade\`\``"
section in the Yocto Project Development Tasks Manual.
.. _devtool-resetting-a-recipe:
diff --git a/documentation/ref-manual/ref-features.rst b/documentation/ref-manual/ref-features.rst
index f28ad2bb4..a16460e91 100644
--- a/documentation/ref-manual/ref-features.rst
+++ b/documentation/ref-manual/ref-features.rst
@@ -273,7 +273,7 @@ these valid features is as follows:
- *tools-debug:* Installs debugging tools such as ``strace`` and
``gdb``. For information on GDB, see the
- ":ref:`platdev-gdb-remotedebug`" section
+ ":ref:`dev-manual/dev-manual-common-tasks:debugging with the gnu project debugger (gdb) remotely`" section
in the Yocto Project Development Tasks Manual. For information on
tracing and profiling, see the :doc:`../profile-manual/profile-manual`.
diff --git a/documentation/ref-manual/ref-structure.rst b/documentation/ref-manual/ref-structure.rst
index db1ea9797..5d17f0e5c 100644
--- a/documentation/ref-manual/ref-structure.rst
+++ b/documentation/ref-manual/ref-structure.rst
@@ -399,8 +399,8 @@ This directory contains any "end result" output from the OpenEmbedded
build process. The :term:`DEPLOY_DIR` variable points
to this directory. For more detail on the contents of the ``deploy``
directory, see the
-":ref:`images-dev-environment`" and
-":ref:`sdk-dev-environment`" sections in the Yocto
+":ref:`overview-manual/overview-manual-concepts:images`" and
+":ref:`overview-manual/overview-manual-concepts:application development sdk`" sections in the Yocto
Project Overview and Concepts Manual.
.. _structure-build-tmp-deploy-deb:
@@ -577,7 +577,7 @@ built within the Yocto Project. For this package, a work directory of
``tmp/work/qemux86-poky-linux/linux-yocto/3.0+git1+<.....>``, referred
to as the ``WORKDIR``, is created. Within this directory, the source is
unpacked to ``linux-qemux86-standard-build`` and then patched by Quilt.
-(See the ":ref:`using-a-quilt-workflow`" section in
+(See the ":ref:`dev-manual/dev-manual-common-tasks:using quilt in your workflow`" section in
the Yocto Project Development Tasks Manual for more information.) Within
the ``linux-qemux86-standard-build`` directory, standard Quilt
directories ``linux-3.0/patches`` and ``linux-3.0/.pc`` are created, and
diff --git a/documentation/ref-manual/ref-tasks.rst b/documentation/ref-manual/ref-tasks.rst
index 88b285d76..299e8f7d6 100644
--- a/documentation/ref-manual/ref-tasks.rst
+++ b/documentation/ref-manual/ref-tasks.rst
@@ -140,7 +140,7 @@ The ``do_image`` task performs pre-processing on the image through the
:term:`IMAGE_PREPROCESS_COMMAND` and
dynamically generates supporting ``do_image_*`` tasks as needed.
-For more information on image creation, see the ":ref:`image-generation-dev-environment`"
+For more information on image creation, see the ":ref:`overview-manual/overview-manual-concepts:image generation`"
section in the Yocto Project Overview and Concepts Manual.
.. _ref-tasks-image-complete:
@@ -159,7 +159,7 @@ through the
:term:`IMAGE_POSTPROCESS_COMMAND`.
For more information on image creation, see the
-":ref:`image-generation-dev-environment`"
+":ref:`overview-manual/overview-manual-concepts:image generation`"
section in the Yocto Project Overview and Concepts Manual.
.. _ref-tasks-install:
@@ -237,7 +237,7 @@ see the :ref:`insane <ref-classes-insane>` class.
Creates Debian packages (i.e. ``*.deb`` files) and places them in the
``${``\ :term:`DEPLOY_DIR_DEB`\ ``}`` directory in
the package feeds area. For more information, see the
-":ref:`package-feeds-dev-environment`" section in
+":ref:`overview-manual/overview-manual-concepts:package feeds`" section in
the Yocto Project Overview and Concepts Manual.
.. _ref-tasks-package_write_ipk:
@@ -248,7 +248,7 @@ the Yocto Project Overview and Concepts Manual.
Creates IPK packages (i.e. ``*.ipk`` files) and places them in the
``${``\ :term:`DEPLOY_DIR_IPK`\ ``}`` directory in
the package feeds area. For more information, see the
-":ref:`package-feeds-dev-environment`" section in
+":ref:`overview-manual/overview-manual-concepts:package feeds`" section in
the Yocto Project Overview and Concepts Manual.
.. _ref-tasks-package_write_rpm:
@@ -259,7 +259,7 @@ the Yocto Project Overview and Concepts Manual.
Creates RPM packages (i.e. ``*.rpm`` files) and places them in the
``${``\ :term:`DEPLOY_DIR_RPM`\ ``}`` directory in
the package feeds area. For more information, see the
-":ref:`package-feeds-dev-environment`" section in
+":ref:`overview-manual/overview-manual-concepts:package feeds`" section in
the Yocto Project Overview and Concepts Manual.
.. _ref-tasks-package_write_tar:
@@ -270,7 +270,7 @@ the Yocto Project Overview and Concepts Manual.
Creates tarballs and places them in the
``${``\ :term:`DEPLOY_DIR_TAR`\ ``}`` directory in
the package feeds area. For more information, see the
-":ref:`package-feeds-dev-environment`" section in
+":ref:`overview-manual/overview-manual-concepts:package feeds`" section in
the Yocto Project Overview and Concepts Manual.
.. _ref-tasks-packagedata:
@@ -349,9 +349,9 @@ patch files end with either ``.patch`` or ``.diff``, every file would be
applied as a patch by default except for the ``patch_file5`` patch.
You can find out more about the patching process in the
-":ref:`patching-dev-environment`" section in
+":ref:`overview-manual/overview-manual-concepts:patching`" section in
the Yocto Project Overview and Concepts Manual and the
-":ref:`new-recipe-patching-code`" section in the
+":ref:`dev-manual/dev-manual-common-tasks:patching code`" section in the
Yocto Project Development Tasks Manual.
.. _ref-tasks-populate_lic:
@@ -368,7 +368,7 @@ the image is constructed.
-------------------
Creates the file and directory structure for an installable SDK. See the
-":ref:`sdk-generation-dev-environment`"
+":ref:`overview-manual/overview-manual-concepts:sdk generation`"
section in the Yocto Project Overview and Concepts Manual for more
information.
@@ -378,7 +378,7 @@ information.
-----------------------
Creates the file and directory structure for an installable extensible
-SDK (eSDK). See the ":ref:`sdk-generation-dev-environment`"
+SDK (eSDK). See the ":ref:`overview-manual/overview-manual-concepts:sdk generation`"
section in the Yocto Project Overview and Concepts Manual for more
information.
@@ -434,7 +434,7 @@ Unpacks the source code into a working directory pointed to by
``${``\ :term:`WORKDIR`\ ``}``. The :term:`S`
variable also plays a role in where unpacked source files ultimately
reside. For more information on how source files are unpacked, see the
-":ref:`source-fetching-dev-environment`"
+":ref:`overview-manual/overview-manual-concepts:source fetching`"
section in the Yocto Project Overview and Concepts Manual and also see
the ``WORKDIR`` and ``S`` variable descriptions.
@@ -567,7 +567,7 @@ scratch is guaranteed.
Starts a shell in which an interactive Python interpreter allows you to
interact with the BitBake build environment. From within this shell, you
can directly examine and set bits from the data store and execute
-functions as if within the BitBake environment. See the ":ref:`platdev-appdev-devpyshell`" section in
+functions as if within the BitBake environment. See the ":ref:`dev-manual/dev-manual-common-tasks:using a development python shell`" section in
the Yocto Project Development Tasks Manual for more information about
using ``devpyshell``.
@@ -577,7 +577,7 @@ using ``devpyshell``.
---------------
Starts a shell whose environment is set up for development, debugging,
-or both. See the ":ref:`platdev-appdev-devshell`" section in the
+or both. See the ":ref:`dev-manual/dev-manual-common-tasks:using a development shell`" section in the
Yocto Project Development Tasks Manual for more information about using
``devshell``.
@@ -593,7 +593,7 @@ Lists all defined tasks for a target.
``do_package_index``
--------------------
-Creates or updates the index in the :ref:`package-feeds-dev-environment` area.
+Creates or updates the index in the :ref:`overview-manual/overview-manual-concepts:package feeds` area.
.. note::
@@ -631,7 +631,7 @@ has some more information about these types of images.
-------------
Creates the root filesystem (file and directory structure) for an image.
-See the ":ref:`image-generation-dev-environment`"
+See the ":ref:`overview-manual/overview-manual-concepts:image generation`"
section in the Yocto Project Overview and Concepts Manual for more
information on how the root filesystem is created.
diff --git a/documentation/ref-manual/ref-variables.rst b/documentation/ref-manual/ref-variables.rst
index 56aeb583a..b24e1fa39 100644
--- a/documentation/ref-manual/ref-variables.rst
+++ b/documentation/ref-manual/ref-variables.rst
@@ -746,7 +746,7 @@ system and gives an overview of their function and contents.
For information on how to use ``BBMULTICONFIG`` in an environment
that supports building targets with multiple configurations, see the
- ":ref:`dev-building-images-for-multiple-targets-using-multiple-configurations`"
+ ":ref:`dev-manual/dev-manual-common-tasks:building images for multiple targets using multiple configurations`"
section in the Yocto Project Development Tasks Manual.
:term:`BBPATH`
@@ -1299,7 +1299,7 @@ system and gives an overview of their function and contents.
will be the aggregate of all of them.
For information on creating an initramfs, see the
- ":ref:`building-an-initramfs-image`" section
+ ":ref:`dev-manual/dev-manual-common-tasks:building an initial ram filesystem (initramfs) image`" section
in the Yocto Project Development Tasks Manual.
:term:`CONFIG_SITE`
@@ -1672,9 +1672,9 @@ system and gives an overview of their function and contents.
For more information on the structure of the Build Directory, see
":ref:`ref-manual/ref-structure:the build directory - \`\`build/\`\``" section.
For more detail on the contents of the ``deploy`` directory, see the
- ":ref:`Images <images-dev-environment>`", ":ref:`Package
- Feeds <package-feeds-dev-environment>`", and
- ":ref:`sdk-dev-environment`" sections all in the
+ ":ref:`overview-manual/overview-manual-concepts:images`",
+ ":ref:`overview-manual/overview-manual-concepts:package feeds`", and
+ ":ref:`overview-manual/overview-manual-concepts:application development sdk`" sections all in the
Yocto Project Overview and Concepts Manual.
:term:`DEPLOY_DIR_DEB`
@@ -1695,8 +1695,8 @@ system and gives an overview of their function and contents.
``DEPLOY_DIR_DEB`` variable to make sure the
:ref:`ref-tasks-package_write_deb` task
writes Debian packages into the appropriate folder. For more
- information on how packaging works, see the ":ref:`Package
- Feeds <package-feeds-dev-environment>`" section
+ information on how packaging works, see the
+ ":ref:`overview-manual/overview-manual-concepts:package feeds`" section
in the Yocto Project Overview and Concepts Manual.
:term:`DEPLOY_DIR_IMAGE`
@@ -1710,8 +1710,8 @@ system and gives an overview of their function and contents.
For more information on the structure of the Build Directory, see
":ref:`ref-manual/ref-structure:the build directory - \`\`build/\`\``" section.
For more detail on the contents of the ``deploy`` directory, see the
- ":ref:`Images <images-dev-environment>`" and
- ":ref:`sdk-dev-environment`" sections both in
+ ":ref:`overview-manual/overview-manual-concepts:images`" and
+ ":ref:`overview-manual/overview-manual-concepts:application development sdk`" sections both in
the Yocto Project Overview and Concepts Manual.
:term:`DEPLOY_DIR_IPK`
@@ -1731,8 +1731,8 @@ system and gives an overview of their function and contents.
``DEPLOY_DIR_IPK`` variable to make sure the
:ref:`ref-tasks-package_write_ipk` task
writes IPK packages into the appropriate folder. For more information
- on how packaging works, see the ":ref:`Package
- Feeds <package-feeds-dev-environment>`" section
+ on how packaging works, see the
+ ":ref:`overview-manual/overview-manual-concepts:package feeds`" section
in the Yocto Project Overview and Concepts Manual.
:term:`DEPLOY_DIR_RPM`
@@ -1752,8 +1752,8 @@ system and gives an overview of their function and contents.
``DEPLOY_DIR_RPM`` variable to make sure the
:ref:`ref-tasks-package_write_rpm` task
writes RPM packages into the appropriate folder. For more information
- on how packaging works, see the ":ref:`Package
- Feeds <package-feeds-dev-environment>`" section
+ on how packaging works, see the
+ ":ref:`overview-manual/overview-manual-concepts:package feeds`" section
in the Yocto Project Overview and Concepts Manual.
:term:`DEPLOY_DIR_TAR`
@@ -1773,8 +1773,8 @@ system and gives an overview of their function and contents.
``DEPLOY_DIR_TAR`` variable to make sure the
:ref:`ref-tasks-package_write_tar` task
writes TAR packages into the appropriate folder. For more information
- on how packaging works, see the ":ref:`Package
- Feeds <package-feeds-dev-environment>`" section
+ on how packaging works, see the
+ ":ref:`overview-manual/overview-manual-concepts:package feeds`" section
in the Yocto Project Overview and Concepts Manual.
:term:`DEPLOYDIR`
@@ -2194,7 +2194,7 @@ system and gives an overview of their function and contents.
Project, see the ":ref:`ref-features-image`" section.
For an example that shows how to customize your image by using this
- variable, see the ":ref:`usingpoky-extend-customimage-imagefeatures`"
+ variable, see the ":ref:`dev-manual/dev-manual-common-tasks:customizing images using custom \`\`image_features\`\` and \`\`extra_image_features\`\``"
section in the Yocto Project Development Tasks Manual.
:term:`EXTRA_IMAGECMD`
@@ -2509,9 +2509,9 @@ system and gives an overview of their function and contents.
build system uses files from ``files/defconfig``.
You can find out more about the patching process in the
- ":ref:`patching-dev-environment`" section
+ ":ref:`overview-manual/overview-manual-concepts:patching`" section
in the Yocto Project Overview and Concepts Manual and the
- ":ref:`new-recipe-patching-code`" section in
+ ":ref:`dev-manual/dev-manual-common-tasks:patching code`" section in
the Yocto Project Development Tasks Manual. See the
:ref:`ref-tasks-patch` task as well.
@@ -3000,7 +3000,7 @@ system and gives an overview of their function and contents.
the ":ref:`ref-features-image`" section.
For an example that shows how to customize your image by using this
- variable, see the ":ref:`usingpoky-extend-customimage-imagefeatures`"
+ variable, see the ":ref:`dev-manual/dev-manual-common-tasks:customizing images using custom \`\`image_features\`\` and \`\`extra_image_features\`\``"
section in the Yocto Project Development Tasks Manual.
:term:`IMAGE_FSTYPES`
@@ -3058,7 +3058,7 @@ system and gives an overview of their function and contents.
allows the initial RAM filesystem (initramfs) recipe to use a
fixed set of packages and not be affected by ``IMAGE_INSTALL``.
For information on creating an initramfs, see the
- ":ref:`building-an-initramfs-image`"
+ ":ref:`dev-manual/dev-manual-common-tasks:building an initial ram filesystem (initramfs) image`"
section in the Yocto Project Development Tasks Manual.
- Using ``IMAGE_INSTALL`` with the
@@ -3126,7 +3126,7 @@ system and gives an overview of their function and contents.
The location is
derived using the :term:`DEPLOY_DIR_IMAGE`
and :term:`IMAGE_NAME` variables. You can find
- information on how the image is created in the ":ref:`image-generation-dev-environment`"
+ information on how the image is created in the ":ref:`overview-manual/overview-manual-concepts:image generation`"
section in the Yocto Project Overview and Concepts Manual.
:term:`IMAGE_NAME`
@@ -3554,7 +3554,7 @@ system and gives an overview of their function and contents.
:term:`INITRAMFS_IMAGE_BUNDLE`
variable, which allows the generated image to be bundled inside the
kernel image. Additionally, for information on creating an initramfs
- image, see the ":ref:`building-an-initramfs-image`" section
+ image, see the ":ref:`dev-manual/dev-manual-common-tasks:building an initial ram filesystem (initramfs) image`" section
in the Yocto Project Development Tasks Manual.
:term:`INITRAMFS_IMAGE_BUNDLE`
@@ -3602,7 +3602,7 @@ system and gives an overview of their function and contents.
See the
:yocto_git:`local.conf.sample.extended </cgit/cgit.cgi/poky/tree/meta-poky/conf/local.conf.sample.extended>`
file for additional information. Also, for information on creating an
- initramfs, see the ":ref:`building-an-initramfs-image`" section
+ initramfs, see the ":ref:`dev-manual/dev-manual-common-tasks:building an initial ram filesystem (initramfs) image`" section
in the Yocto Project Development Tasks Manual.
:term:`INITRAMFS_LINK_NAME`
@@ -4240,7 +4240,7 @@ system and gives an overview of their function and contents.
This variable must be defined for all recipes (unless
:term:`LICENSE` is set to "CLOSED").
- For more information, see the ":ref:`usingpoky-configuring-lic_files_chksum`"
+ For more information, see the ":ref:`dev-manual/dev-manual-common-tasks:tracking license changes`"
section in the Yocto Project Development Tasks Manual.
:term:`LICENSE`
@@ -4890,7 +4890,7 @@ system and gives an overview of their function and contents.
Controls how the OpenEmbedded build system spawns interactive
terminals on the host development system (e.g. using the BitBake
command with the ``-c devshell`` command-line option). For more
- information, see the ":ref:`platdev-appdev-devshell`" section in
+ information, see the ":ref:`dev-manual/dev-manual-common-tasks:using a development shell`" section in
the Yocto Project Development Tasks Manual.
You can use the following values for the ``OE_TERMINAL`` variable:
@@ -4959,7 +4959,7 @@ system and gives an overview of their function and contents.
An easy way to see what overrides apply is to search for ``OVERRIDES``
in the output of the ``bitbake -e`` command. See the
- ":ref:`dev-debugging-viewing-variable-values`" section in the Yocto
+ ":ref:`dev-manual/dev-manual-common-tasks:viewing variable values`" section in the Yocto
Project Development Tasks Manual for more information.
:term:`P`
@@ -5079,7 +5079,7 @@ system and gives an overview of their function and contents.
separate ``*-src`` pkg. This is the default behavior.
You can find out more about debugging using GDB by reading the
- ":ref:`platdev-gdb-remotedebug`" section
+ ":ref:`dev-manual/dev-manual-common-tasks:debugging with the gnu project debugger (gdb) remotely`" section
in the Yocto Project Development Tasks Manual.
:term:`PACKAGE_EXCLUDE_COMPLEMENTARY`
@@ -5243,7 +5243,7 @@ system and gives an overview of their function and contents.
the :ref:`core-image-minimal-initramfs <ref-manual/ref-images:images>`
image. When working with an initial RAM filesystem (initramfs) image,
use the ``PACKAGE_INSTALL`` variable. For information on creating an
- initramfs, see the ":ref:`building-an-initramfs-image`" section
+ initramfs, see the ":ref:`dev-manual/dev-manual-common-tasks:building an initial ram filesystem (initramfs) image`" section
in the Yocto Project Development Tasks Manual.
:term:`PACKAGE_INSTALL_ATTEMPTONLY`
@@ -5691,7 +5691,7 @@ system and gives an overview of their function and contents.
The OpenEmbedded build system does not need the aid of ``PR``
to know when to rebuild a recipe. The build system uses the task
- :ref:`input checksums <overview-checksums>` along with the
+ :ref:`input checksums <overview-manual/overview-manual-concepts:checksums (signatures)>` along with the
:ref:`stamp <structure-build-tmp-stamps>` and
:ref:`overview-manual/overview-manual-concepts:shared state cache`
mechanisms.
@@ -5738,7 +5738,7 @@ system and gives an overview of their function and contents.
PREFERRED_PROVIDER_virtual/libgl ?= "mesa"
For more
- information, see the ":ref:`metadata-virtual-providers`"
+ information, see the ":ref:`dev-manual/dev-manual-common-tasks:using virtual providers`"
section in the Yocto Project Development Tasks Manual.
.. note::
@@ -7023,7 +7023,7 @@ system and gives an overview of their function and contents.
- ``file://`` - Fetches files, which are usually files shipped
with the :term:`Metadata`, from the local machine (e.g.
- :ref:`patch <patching-dev-environment>` files).
+ :ref:`patch <overview-manual/overview-manual-concepts:patching>` files).
The path is relative to the :term:`FILESPATH`
variable. Thus, the build system searches, in order, from the
following directories, which are assumed to be a subdirectories of
@@ -7200,7 +7200,7 @@ system and gives an overview of their function and contents.
For information on limitations when inheriting the latest revision
of software using ``SRCREV``, see the :term:`AUTOREV` variable
description and the
- ":ref:`automatically-incrementing-a-binary-package-revision-number`"
+ ":ref:`dev-manual/dev-manual-common-tasks:automatically incrementing a package version number`"
section, which is in the Yocto Project Development Tasks Manual.
:term:`SSTATE_DIR`
@@ -7316,7 +7316,7 @@ system and gives an overview of their function and contents.
see the :ref:`ref-tasks-populate_sysroot`
task, the ":ref:`sdk-manual/sdk-extensible:sharing files between recipes`"
section in the Yocto Project Development Tasks Manual, the
- ":ref:`configuration-compilation-and-staging-dev-environment`"
+ ":ref:`overview-manual/overview-manual-concepts:configuration, compilation, and staging`"
section in the Yocto Project Overview and Concepts Manual, and the
:term:`SYSROOT_DIRS` variable.
@@ -8042,7 +8042,7 @@ system and gives an overview of their function and contents.
You can provide the following arguments with ``TEST_TARGET``:
- *"qemu":* Boots a QEMU image and runs the tests. See the
- ":ref:`qemu-image-enabling-tests`" section
+ ":ref:`dev-manual/dev-manual-common-tasks:enabling runtime tests on qemu`" section
in the Yocto Project Development Tasks Manual for more
information.
@@ -8058,7 +8058,7 @@ system and gives an overview of their function and contents.
``meta/lib/oeqa/controllers/simpleremote.py``.
For information on running tests on hardware, see the
- ":ref:`hardware-image-enabling-tests`"
+ ":ref:`dev-manual/dev-manual-common-tasks:enabling runtime tests on hardware`"
section in the Yocto Project Development Tasks Manual.
:term:`TEST_TARGET_IP`
@@ -8554,13 +8554,13 @@ system and gives an overview of their function and contents.
specifically set. Typically, you would set ``USE_DEVFS`` to "0" for a
statically populated ``/dev`` directory.
- See the ":ref:`selecting-dev-manager`" section in
+ See the ":ref:`dev-manual/dev-manual-common-tasks:selecting a device manager`" section in
the Yocto Project Development Tasks Manual for information on how to
use this variable.
:term:`USE_VT`
When using
- :ref:`SysVinit <new-recipe-enabling-system-services>`,
+ :ref:`SysVinit <dev-manual/dev-manual-common-tasks:enabling system services>`,
determines whether or not to run a
`getty <http://en.wikipedia.org/wiki/Getty_%28Unix%29>`__ on any
virtual terminals in order to enable logging in through those
diff --git a/documentation/ref-manual/resources.rst b/documentation/ref-manual/resources.rst
index 2ef182fb1..c172aab25 100644
--- a/documentation/ref-manual/resources.rst
+++ b/documentation/ref-manual/resources.rst
@@ -23,7 +23,7 @@ The Yocto Project gladly accepts contributions. You can submit changes
to the project either by creating and sending pull requests, or by
submitting patches through email. For information on how to do both as
well as information on how to identify the maintainer for each area of
-code, see the ":ref:`how-to-submit-a-change`" section in the
+code, see the ":ref:`dev-manual/dev-manual-common-tasks:submitting a change to the yocto project`" section in the
Yocto Project Development Tasks Manual.
.. _resources-bugtracker:
--
2.29.2
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH 5/7] sdk-manual: replace labels with references to section title
2020-11-26 9:48 [PATCH 0/7] A second pass at removing labels Nicolas Dechesne
` (3 preceding siblings ...)
2020-11-26 9:48 ` [PATCH 4/7] ref-manual: " Nicolas Dechesne
@ 2020-11-26 9:48 ` Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 6/7] overview-manual: remove unused labels Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 7/7] dev-manual: " Nicolas Dechesne
6 siblings, 0 replies; 8+ messages in thread
From: Nicolas Dechesne @ 2020-11-26 9:48 UTC (permalink / raw)
To: docs; +Cc: Nicolas Dechesne
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
---
documentation/sdk-manual/sdk-appendix-obtain.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/sdk-manual/sdk-appendix-obtain.rst b/documentation/sdk-manual/sdk-appendix-obtain.rst
index 1a2e4c387..6b7128c27 100644
--- a/documentation/sdk-manual/sdk-appendix-obtain.rst
+++ b/documentation/sdk-manual/sdk-appendix-obtain.rst
@@ -91,7 +91,7 @@ build the SDK installer. Follow these steps:
(i.e. a local
``poky`` repository). See the ":ref:`dev-manual/dev-manual-start:cloning the \`\`poky\`\` repository`" and
possibly the ":ref:`dev-manual/dev-manual-start:checking out by branch in poky`" and
- ":ref:`checkout-out-by-tag-in-poky`" sections
+ ":ref:`dev-manual/dev-manual-start:checking out by tag in poky`" sections
all in the Yocto Project Development Tasks Manual for information on
how to clone the ``poky`` repository and check out the appropriate
branch for your work.
--
2.29.2
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH 6/7] overview-manual: remove unused labels
2020-11-26 9:48 [PATCH 0/7] A second pass at removing labels Nicolas Dechesne
` (4 preceding siblings ...)
2020-11-26 9:48 ` [PATCH 5/7] sdk-manual: " Nicolas Dechesne
@ 2020-11-26 9:48 ` Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 7/7] dev-manual: " Nicolas Dechesne
6 siblings, 0 replies; 8+ messages in thread
From: Nicolas Dechesne @ 2020-11-26 9:48 UTC (permalink / raw)
To: docs; +Cc: Nicolas Dechesne
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
---
.../overview-manual-concepts.rst | 40 -------------------
...verview-manual-development-environment.rst | 6 ---
.../overview-manual/overview-manual-intro.rst | 4 --
.../overview-manual-yp-intro.rst | 22 ----------
4 files changed, 72 deletions(-)
diff --git a/documentation/overview-manual/overview-manual-concepts.rst b/documentation/overview-manual/overview-manual-concepts.rst
index f1f2b7f35..353a2f99f 100644
--- a/documentation/overview-manual/overview-manual-concepts.rst
+++ b/documentation/overview-manual/overview-manual-concepts.rst
@@ -43,8 +43,6 @@ see the
":ref:`overview-manual/overview-manual-concepts:openembedded build system concepts`"
section.
-.. _usingpoky-components-bitbake:
-
BitBake
-------
@@ -92,8 +90,6 @@ occurs, the target that failed and those that depend on it cannot be
remade. However, when you use this option other dependencies can still
be processed.
-.. _overview-components-recipes:
-
Recipes
-------
@@ -109,8 +105,6 @@ the word "package" is used for the packaged output from the OpenEmbedded
build system (i.e. ``.ipk`` or ``.deb`` files), this document avoids
using the term "package" when referring to recipes.
-.. _overview-components-classes:
-
Classes
-------
@@ -122,8 +116,6 @@ The ":ref:`ref-manual/ref-classes:Classes`" chapter in the
Yocto Project Reference Manual provides details about classes and how to
use them.
-.. _overview-components-configurations:
-
Configurations
--------------
@@ -135,8 +127,6 @@ common configuration options, and user configuration options in
``conf/local.conf``, which is found in the :term:`Build Directory`.
-.. _overview-layers:
-
Layers
======
@@ -166,8 +156,6 @@ layers suitable for the Yocto Project in the
":ref:`dev-manual/dev-manual-common-tasks:understanding and creating layers`"
section of the Yocto Project Development Tasks Manual.
-.. _openembedded-build-system-build-concepts:
-
OpenEmbedded Build System Concepts
==================================
@@ -527,8 +515,6 @@ their respective layers.
This layer contains any recipes, append files, and patches, that your
project needs.
-.. _sources-dev-environment:
-
Sources
-------
@@ -601,8 +587,6 @@ class to include that local project. You use either the ``local.conf``
or a recipe's append file to override or set the recipe to point to the
local directory on your disk to pull in the whole source tree.
-.. _scms:
-
Source Control Managers (Optional)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -644,8 +628,6 @@ Regular mirrors can be any site across the Internet that is used as an
alternative location for source code should the primary site not be
functioning for some reason or another.
-.. _package-feeds-dev-environment:
-
Package Feeds
-------------
@@ -709,8 +691,6 @@ qemux86 exist. Packages for the i586 architecture are placed in
``build/tmp/deploy/ipk/i586``, while packages for the qemux86
architecture are placed in ``build/tmp/deploy/ipk/qemux86``.
-.. _bitbake-dev-environment:
-
BitBake Tool
------------
@@ -727,8 +707,6 @@ those areas.
BitBake User Manual
for reference material on BitBake.
-.. _source-fetching-dev-environment:
-
Source Fetching
~~~~~~~~~~~~~~~
@@ -819,8 +797,6 @@ Build Directory's hierarchy:
what the OpenEmbedded build system is using as a build target (e.g.
general architecture, a build host, an SDK, or a specific machine).
-.. _patching-dev-environment:
-
Patching
~~~~~~~~
@@ -861,8 +837,6 @@ Software Development Kit (SDK) manual and the
":ref:`kernel-dev/kernel-dev-common:using traditional kernel development to patch the kernel`"
section in the Yocto Project Linux Kernel Development Manual.
-.. _configuration-compilation-and-staging-dev-environment:
-
Configuration, Compilation, and Staging
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -922,8 +896,6 @@ This step in the build process consists of the following tasks:
variable. Packaging occurs later using files from this holding
directory.
-.. _package-splitting-dev-environment:
-
Package Splitting
~~~~~~~~~~~~~~~~~
@@ -1004,8 +976,6 @@ that part of the build process.
functionality is highly distribution-specific and thus is not
provided out of the box.
-.. _image-generation-dev-environment:
-
Image Generation
~~~~~~~~~~~~~~~~
@@ -1127,8 +1097,6 @@ build system has created the final image output files.
Pseudo. Running under Pseudo ensures that the files in the root filesystem
have correct ownership.
-.. _sdk-generation-dev-environment:
-
SDK Generation
~~~~~~~~~~~~~~
@@ -1303,8 +1271,6 @@ variable is the function that determines whether a given dependency
needs to be followed, and whether for any given relationship the
function needs to be passed. The function returns a True or False value.
-.. _images-dev-environment:
-
Images
------
@@ -1363,8 +1329,6 @@ current configuration.
These links might be useful for external scripts that need to obtain
the latest version of each file.
-.. _sdk-dev-environment:
-
Application Development SDK
---------------------------
@@ -1677,8 +1641,6 @@ them if they are deemed to be valid.
The rest of this section goes into detail about the overall incremental
build architecture, the checksums (signatures), and shared state.
-.. _concepts-overall-architecture:
-
Overall Architecture
--------------------
@@ -1697,8 +1659,6 @@ specific tasks. This methodology does not scale well and does not allow
users to easily add new tasks in layers or as external recipes without
touching the packaged-staging core.
-.. _overview-checksums:
-
Checksums (Signatures)
----------------------
diff --git a/documentation/overview-manual/overview-manual-development-environment.rst b/documentation/overview-manual/overview-manual-development-environment.rst
index 4bedd6df6..983e1919e 100644
--- a/documentation/overview-manual/overview-manual-development-environment.rst
+++ b/documentation/overview-manual/overview-manual-development-environment.rst
@@ -45,8 +45,6 @@ also find helpful information on how to participate in the Linux
Community
`here <https://www.kernel.org/doc/html/latest/process/index.html>`__.
-.. _gs-the-development-host:
-
The Development Host
====================
@@ -134,8 +132,6 @@ methods exist for you to do work in the Yocto Project environment:
Toaster and on how to use Toaster in general, see the
:doc:`../toaster-manual/toaster-manual`.
-.. _yocto-project-repositories:
-
Yocto Project Source Repositories
=================================
@@ -214,8 +210,6 @@ development:
":ref:`dev-manual/dev-manual-start:using the downloads page`"
section in the Yocto Project Development Tasks Manual.
-.. _gs-git-workflows-and-the-yocto-project:
-
Git Workflows and the Yocto Project
===================================
diff --git a/documentation/overview-manual/overview-manual-intro.rst b/documentation/overview-manual/overview-manual-intro.rst
index 8885eb89f..f69824da9 100644
--- a/documentation/overview-manual/overview-manual-intro.rst
+++ b/documentation/overview-manual/overview-manual-intro.rst
@@ -4,8 +4,6 @@
The Yocto Project Overview and Concepts Manual
**********************************************
-.. _overview-manual-welcome:
-
Welcome
=======
@@ -57,8 +55,6 @@ This manual does not give you the following:
Manager Git is better covered with Internet searches and official Git
Documentation than through the Yocto Project documentation.
-.. _overview-manual-other-information:
-
Other Information
=================
diff --git a/documentation/overview-manual/overview-manual-yp-intro.rst b/documentation/overview-manual/overview-manual-yp-intro.rst
index 9073582ac..83ed18a37 100644
--- a/documentation/overview-manual/overview-manual-yp-intro.rst
+++ b/documentation/overview-manual/overview-manual-yp-intro.rst
@@ -35,8 +35,6 @@ by Drew Moseley and in this short introductory
The remainder of this section overviews advantages and challenges tied
to the Yocto Project.
-.. _gs-features:
-
Features
--------
@@ -136,8 +134,6 @@ Project:
for review by people who need to track the use of open source
licenses (e.g. legal teams).
-.. _gs-challenges:
-
Challenges
----------
@@ -296,8 +292,6 @@ components and tools are downloaded separately.
This section provides brief overviews of the components and tools
associated with the Yocto Project.
-.. _gs-development-tools:
-
Development Tools
-----------------
@@ -353,8 +347,6 @@ applications using the Yocto Project:
view information about builds. For information on Toaster, see the
:doc:`../toaster-manual/toaster-manual`.
-.. _gs-production-tools:
-
Production Tools
----------------
@@ -450,8 +442,6 @@ activities using the Yocto Project:
You can read more about Pseudo in the "`Fakeroot and
Pseudo <#fakeroot-and-pseudo>`__" section.
-.. _gs-openembedded-build-system:
-
Open-Embedded Build System Components
-------------------------------------
@@ -496,8 +486,6 @@ The following list consists of components associated with the
components such as BitBake, OE-Core, script "glue", and documentation
for its build system.
-.. _gs-reference-distribution-poky:
-
Reference Distribution (Poky)
-----------------------------
@@ -520,8 +508,6 @@ To use the Yocto Project tools and components, you can download
You can read more about Poky in the "`Reference Embedded Distribution
(Poky) <#reference-embedded-distribution>`__" section.
-.. _gs-packages-for-finished-targets:
-
Packages for Finished Targets
-----------------------------
@@ -560,8 +546,6 @@ targets:
You can find the opkg source in the Yocto Project
:yocto_git:`Source Repositories <>`.
-.. _gs-archived-components:
-
Archived Components
-------------------
@@ -588,8 +572,6 @@ Linux.
using the Yocto Project on a system not native to Linux is with
`CROPS <#gs-crops-overview>`__.
-.. _gs-development-methods:
-
Development Methods
===================
@@ -671,8 +653,6 @@ Project.
For information about and how to use Toaster, see the
:doc:`../toaster-manual/toaster-manual`.
-.. _reference-embedded-distribution:
-
Reference Embedded Distribution (Poky)
======================================
@@ -776,8 +756,6 @@ operators, see the
":ref:`bitbake:bitbake-user-manual/bitbake-user-manual-metadata:appending and prepending (override style syntax)`"
section in the BitBake User's Manual.
-.. _openembedded-build-system-workflow:
-
The OpenEmbedded Build System Workflow
======================================
--
2.29.2
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH 7/7] dev-manual: remove unused labels
2020-11-26 9:48 [PATCH 0/7] A second pass at removing labels Nicolas Dechesne
` (5 preceding siblings ...)
2020-11-26 9:48 ` [PATCH 6/7] overview-manual: remove unused labels Nicolas Dechesne
@ 2020-11-26 9:48 ` Nicolas Dechesne
6 siblings, 0 replies; 8+ messages in thread
From: Nicolas Dechesne @ 2020-11-26 9:48 UTC (permalink / raw)
To: docs; +Cc: Nicolas Dechesne
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
---
.../dev-manual/dev-manual-common-tasks.rst | 220 ------------------
documentation/dev-manual/dev-manual-intro.rst | 2 -
documentation/dev-manual/dev-manual-qemu.rst | 14 --
documentation/dev-manual/dev-manual-start.rst | 10 -
4 files changed, 246 deletions(-)
diff --git a/documentation/dev-manual/dev-manual-common-tasks.rst b/documentation/dev-manual/dev-manual-common-tasks.rst
index 23c2be4f4..706d5e7a6 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.rst
+++ b/documentation/dev-manual/dev-manual-common-tasks.rst
@@ -160,8 +160,6 @@ Follow these general steps to create your layer without using tools:
Project <#making-sure-your-layer-is-compatible-with-yocto-project>`__"
section for more information.
-.. _best-practices-to-follow-when-creating-layers:
-
Following Best Practices When Creating Layers
---------------------------------------------
@@ -457,8 +455,6 @@ file. During the processing of each ``conf/layer.conf`` file, BitBake
adds the recipes, classes and configurations contained within the
particular layer to the source directory.
-.. _using-bbappend-files:
-
Using .bbappend Files in Your Layer
-----------------------------------
@@ -839,16 +835,12 @@ enables the build system to locate the layer during the build.
During a build, the OpenEmbedded build system looks in the layers
from the top of the list down to the bottom in that order.
-.. _usingpoky-extend-customimage:
-
Customizing Images
==================
You can customize images to satisfy particular requirements. This
section describes several methods and provides guidelines for each.
-.. _usingpoky-extend-customimage-localconf:
-
Customizing Images Using ``local.conf``
---------------------------------------
@@ -891,8 +883,6 @@ You can add packages using a similar approach through the
``CORE_IMAGE_EXTRA_INSTALL`` variable. If you use this variable, only
``core-image-*`` images are affected.
-.. _usingpoky-extend-customimage-imagefeatures:
-
Customizing Images Using Custom ``IMAGE_FEATURES`` and ``EXTRA_IMAGE_FEATURES``
-------------------------------------------------------------------------------
@@ -949,8 +939,6 @@ configures the image you are working with to include
Project Reference Manual for a complete list of image features that ship
with the Yocto Project.
-.. _usingpoky-extend-customimage-custombb:
-
Customizing Images Using Custom .bb Files
-----------------------------------------
@@ -977,8 +965,6 @@ image, copy the ``meta/recipes-sato/images/core-image-sato.bb`` to a new
IMAGE_INSTALL += "strace"
-.. _usingpoky-extend-customimage-customtasks:
-
Customizing Images Using Custom Package Groups
----------------------------------------------
@@ -1039,8 +1025,6 @@ build an image using these package group packages, you need to add
``IMAGE_INSTALL``. For other forms of image dependencies see the other
areas of this section.
-.. _usingpoky-extend-customimage-image-name:
-
Customizing an Image Hostname
-----------------------------
@@ -1080,8 +1064,6 @@ unsets the variable in a configuration file:
Having no default hostname in the filesystem is suitable for
environments that use dynamic hostnames such as virtual machines.
-.. _new-recipe-writing-a-new-recipe:
-
Writing a New Recipe
====================
@@ -1097,8 +1079,6 @@ how to create, write, and test a new recipe.
":ref:`ref-manual/ref-varlocality:recipes`" section of the Yocto Project
Reference Manual.
-.. _new-recipe-overview:
-
Overview
--------
@@ -1108,8 +1088,6 @@ The remainder of the section provides details for the steps.
.. image:: figures/recipe-workflow.png
:align: center
-.. _new-recipe-locate-or-automatically-create-a-base-recipe:
-
Locate or Automatically Create a Base Recipe
--------------------------------------------
@@ -1130,8 +1108,6 @@ that can help you quickly get a start on a new recipe:
For information on recipe syntax, see the
":ref:`dev-manual/dev-manual-common-tasks:recipe syntax`" section.
-.. _new-recipe-creating-the-base-recipe-using-devtool:
-
Creating the Base Recipe Using ``devtool add``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -1147,8 +1123,6 @@ the ":ref:`sdk-manual/sdk-extensible:a closer look at \`\`devtool add\`\``" sect
in the Yocto Project Application Development and the Extensible Software
Development Kit (eSDK) manual.
-.. _new-recipe-creating-the-base-recipe-using-recipetool:
-
Creating the Base Recipe Using ``recipetool create``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -1213,8 +1187,6 @@ Following are some syntax examples:
recipetool create -d -o OUTFILE source
-.. _new-recipe-locating-and-using-a-similar-recipe:
-
Locating and Using a Similar Recipe
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -1254,8 +1226,6 @@ get started. Here are some points on both methods:
SRC_URI = ""
-.. _new-recipe-storing-and-naming-the-recipe:
-
Storing and Naming the Recipe
-----------------------------
@@ -1298,8 +1268,6 @@ the recipe.
gawk_4.0.2.bb
irssi_0.8.16-rc1.bb
-.. _new-recipe-running-a-build-on-the-recipe:
-
Running a Build on the Recipe
-----------------------------
@@ -1354,8 +1322,6 @@ You can find more information about the build process in
":doc:`../overview-manual/overview-manual-development-environment`"
chapter of the Yocto Project Overview and Concepts Manual.
-.. _new-recipe-fetching-code:
-
Fetching Code
-------------
@@ -1490,8 +1456,6 @@ compressed suffixes such as ``diff.gz`` and ``patch.bz2``, for example.
The build system automatically applies patches as described in the
"`Patching Code <#new-recipe-patching-code>`__" section.
-.. _new-recipe-unpacking-code:
-
Unpacking Code
--------------
@@ -1512,8 +1476,6 @@ If processing your recipe using BitBake successfully unpacks the source
files, you need to be sure that the directory pointed to by ``${S}``
matches the structure of the source.
-.. _new-recipe-patching-code:
-
Patching Code
-------------
@@ -1539,8 +1501,6 @@ named the same as the base name of the recipe
(:term:`BP` and
:term:`BPN`) or "files".
-.. _new-recipe-licensing:
-
Licensing
---------
@@ -1597,8 +1557,6 @@ variables:
correct string that you can substitute into the recipe file for a
subsequent build.
-.. _new-dependencies:
-
Dependencies
------------
@@ -1645,8 +1603,6 @@ system will automatically add a runtime dependency to "mypackage" on
section in the Yocto Project Overview and Concepts Manual for further
details.
-.. _new-recipe-configuring-the-recipe:
-
Configuring the Recipe
----------------------
@@ -1741,8 +1697,6 @@ the software you are building, you can consult the output of the
``./configure --help`` command within ``${S}`` or consult the software's
upstream documentation.
-.. _new-recipe-using-headers-to-interface-with-devices:
-
Using Headers to Interface with Devices
---------------------------------------
@@ -1802,8 +1756,6 @@ out-of-tree modules. Your recipe will also need the following:
do_configure[depends] += "virtual/kernel:do_shared_workdir"
-.. _new-recipe-compilation:
-
Compilation
-----------
@@ -1867,8 +1819,6 @@ Here are some common issues that cause failures.
``STAGING_BINDIR``, ``STAGING_INCDIR``, ``STAGING_DATADIR``, and so
forth).
-.. _new-recipe-installing:
-
Installing
----------
@@ -1956,8 +1906,6 @@ installed correctly.
files to ``${D}${datadir}/cmake/Modules`` during
:ref:`ref-tasks-install`.
-.. _new-recipe-enabling-system-services:
-
Enabling System Services
------------------------
@@ -2009,8 +1957,6 @@ different ways:
section for
more information.
-.. _new-recipe-packaging:
-
Packaging
---------
@@ -2089,8 +2035,6 @@ take. The following list describes the process:
target machine, particularly if you run separate builds for more than
one target machine.
-.. _new-sharing-files-between-recipes:
-
Sharing Files Between Recipes
-----------------------------
@@ -2137,8 +2081,6 @@ For a more complete description of the
task and its associated functions, see the
:ref:`staging <ref-classes-staging>` class.
-.. _metadata-virtual-providers:
-
Using Virtual Providers
-----------------------
@@ -2251,8 +2193,6 @@ example:
REALPV = "0.8.16-rc1"
PV = "0.8.15+${REALPV}"
-.. _new-recipe-post-installation-scripts:
-
Post-Installation Scripts
-------------------------
@@ -2313,8 +2253,6 @@ script to first boot is undesirable and for read-only rootfs impossible.
because of when they run, they are not applicable to being run at image
creation time like ``pkg_postinst``.
-.. _new-recipe-testing:
-
Testing
-------
@@ -2326,8 +2264,6 @@ For information on how to customize your image by adding specific
packages, see the "`Customizing
Images <#usingpoky-extend-customimage>`__" section.
-.. _new-recipe-testing-examples:
-
Examples
--------
@@ -2344,8 +2280,6 @@ examples given various scenarios:
- Adding binaries to an image
-.. _new-recipe-single-c-file-package-hello-world:
-
Single .c File Package (Hello World!)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -2382,8 +2316,6 @@ customize the packaging process, see the "`Splitting an Application into
Multiple Packages <#splitting-an-application-into-multiple-packages>`__"
section.
-.. _new-recipe-autotooled-package:
-
Autotooled Package
~~~~~~~~~~~~~~~~~~
@@ -2413,8 +2345,6 @@ changes as described in the
the Yocto Project Overview and Concepts Manual. You can quickly create
Autotool-based recipes in a manner similar to the previous example.
-.. _new-recipe-makefile-based-package:
-
Makefile-Based Package
~~~~~~~~~~~~~~~~~~~~~~
@@ -2864,8 +2794,6 @@ in the BitBake User Manual.
might wish to use. If in doubt, you should check with multiple
implementations - including those from BusyBox.
-.. _platdev-newmachine:
-
Adding a New Machine
====================
@@ -2885,8 +2813,6 @@ For a complete example that shows how to add a new machine, see the
section in the Yocto Project Board Support Package (BSP) Developer's
Guide.
-.. _platdev-newmachine-conffile:
-
Adding the Machine Configuration File
-------------------------------------
@@ -2920,8 +2846,6 @@ You can find full details on these variables in the reference section.
You can leverage existing machine ``.conf`` files from
``meta-yocto-bsp/conf/machine/``.
-.. _platdev-newmachine-kernel:
-
Adding a Kernel for the Machine
-------------------------------
@@ -2956,8 +2880,6 @@ For more information on ``defconfig`` files, see the
":ref:`kernel-dev/kernel-dev-common:changing the configuration`"
section in the Yocto Project Linux Kernel Development Manual.
-.. _platdev-newmachine-formfactor:
-
Adding a Formfactor Configuration File
--------------------------------------
@@ -2990,8 +2912,6 @@ Following is an example for "qemuarm" machine:
DISPLAY_DPI=150
DISPLAY_SUBPIXEL_ORDER=vrgb
-.. _gs-upgrading-recipes:
-
Upgrading Recipes
=================
@@ -3011,8 +2931,6 @@ automatic version upgrades. Alternatively, you can use
``devtool upgrade`` to set up semi-automatic version upgrades. Finally,
you can manually upgrade a recipe by editing the recipe itself.
-.. _gs-using-the-auto-upgrade-helper:
-
Using the Auto Upgrade Helper (AUH)
-----------------------------------
@@ -3207,8 +3125,6 @@ a cron job. See the
:yocto_git:`weeklyjob.sh </cgit/cgit.cgi/auto-upgrade-helper/tree/weeklyjob.sh>`
file distributed with the utility for an example.
-.. _gs-using-devtool-upgrade:
-
Using ``devtool upgrade``
-------------------------
@@ -3350,8 +3266,6 @@ Using the ``devtool finish`` command cleans up the workspace and creates a patch
file based on your commits. The tool puts all patch files back into the
source directory in a sub-directory named ``nano`` in this case.
-.. _dev-manually-upgrading-a-recipe:
-
Manually Upgrading a Recipe
---------------------------
@@ -3419,8 +3333,6 @@ To manually upgrade recipe versions, follow these general steps:
builds work and any testing is successful, you can create commits for
any changes in the layer holding your upgraded recipe.
-.. _finding-the-temporary-source-code:
-
Finding Temporary Source Code
=============================
@@ -3491,8 +3403,6 @@ build system uses to build the package would be as follows:
poky/build/tmp/work/qemux86-poky-linux/foo/1.3.0-r0
-.. _using-a-quilt-workflow:
-
Using Quilt in Your Workflow
============================
@@ -3587,8 +3497,6 @@ Follow these general steps:
SRC_URI += "file://my_changes.patch"
-.. _platdev-appdev-devshell:
-
Using a Development Shell
=========================
@@ -3671,8 +3579,6 @@ terminal window.
- It is also worth noting that ``devshell`` still works over X11
forwarding and similar situations.
-.. _platdev-appdev-devpyshell:
-
Using a Development Python Shell
================================
@@ -3720,8 +3626,6 @@ controls what type of shell is opened.
When you are finished using ``devpyshell``, you can exit the shell
either by using Ctrl+d or closing the terminal window.
-.. _dev-building:
-
Building
========
@@ -3729,8 +3633,6 @@ This section describes various build procedures. For example, the steps
needed for a simple build, a target that uses multiple configurations,
building an image for more than one machine, and so forth.
-.. _dev-building-a-simple-image:
-
Building a Simple Image
-----------------------
@@ -3833,8 +3735,6 @@ The following figure and list overviews the build process:
information about how to install these images, see the documentation
for your particular board or machine.
-.. _dev-building-images-for-multiple-targets-using-multiple-configurations:
-
Building Images for Multiple Targets Using Multiple Configurations
------------------------------------------------------------------
@@ -3848,8 +3748,6 @@ This section describes how to set up for multiple configuration builds
and how to account for cross-build dependencies between the
multiconfigs.
-.. _dev-setting-up-and-running-a-multiple-configuration-build:
-
Setting Up and Running a Multiple Configuration Build
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -3942,8 +3840,6 @@ Follow these steps to set up and execute multiple configuration builds:
directories, the build either loads from an existing sstate cache for
that build at the start or builds the object fresh.
-.. _dev-enabling-multiple-configuration-build-dependencies:
-
Enabling Multiple Configuration Build Dependencies
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -4003,8 +3899,6 @@ and have separate configuration files, BitBake places the artifacts for
each build in the respective temporary build directories (i.e.
:term:`TMPDIR`).
-.. _building-an-initramfs-image:
-
Building an Initial RAM Filesystem (initramfs) Image
----------------------------------------------------
@@ -4095,8 +3989,6 @@ distribution to even smaller sizes than the ``poky-tiny`` distribution,
which is around 5 Mbytes, that can be built out-of-the-box using the
Yocto Project.
-.. _tiny-system-overview:
-
Tiny System Overview
~~~~~~~~~~~~~~~~~~~~
@@ -4145,8 +4037,6 @@ very small distributions:
information on how to create layers, see the "`Understanding and
Creating Layers <#understanding-and-creating-layers>`__" section.
-.. _understand-what-gives-your-image-size:
-
Understand What Contributes to Your Image Size
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -4812,8 +4702,6 @@ that can help you speed up the build:
the static libraries. If so, you might need to exclude them as
well.
-.. _platdev-working-with-libraries:
-
Working With Libraries
======================
@@ -4889,8 +4777,6 @@ how the static library files are defined:
SECTION_${PN}-staticdev = "devel"
RDEPENDS_${PN}-staticdev = "${PN}-dev (= ${EXTENDPKGV})"
-.. _combining-multiple-versions-library-files-into-one-image:
-
Combining Multiple Versions of Library Files into One Image
-----------------------------------------------------------
@@ -5299,8 +5185,6 @@ The following know issues exist for GObject Introspection Support:
under 32-bit host machines. In particular, "qemumips64" is known to
not work under i686.
-.. _dev-optionally-using-an-external-toolchain:
-
Optionally Using an External Toolchain
======================================
@@ -5368,8 +5252,6 @@ you need to have in place to run the tool, provides instruction on how
to use the Wic utility, provides information on using the Wic plugins
interface, and provides several examples that show how to use Wic.
-.. _wic-background:
-
Background
----------
@@ -5395,8 +5277,6 @@ this information is required to use Wic, you might find it interesting.
general-purpose partitioning language, which is based on Redhat
kickstart syntax.
-.. _wic-requirements:
-
Requirements
------------
@@ -5435,8 +5315,6 @@ system needs to meet the following requirements:
- Include the name of the :ref:`wic kickstart file <openembedded-kickstart-wks-reference>`
as part of the :term:`WKS_FILE` variable
-.. _wic-getting-help:
-
Getting Help
------------
@@ -5610,8 +5488,6 @@ The general form of the ``wic`` command using Cooked Mode is as follows:
name of the image to use the artifacts from e.g. core-
image-sato
-.. _using-a-provided-kickstart-file:
-
Using an Existing Kickstart File
--------------------------------
@@ -5661,8 +5537,6 @@ Here are the actual partition language commands used in the
bootloader --ptable gpt --timeout=5 --append="rootfstype=ext4 console=ttyS0,115200 console=tty0"
-.. _wic-using-the-wic-plugin-interface:
-
Using the Wic Plugin Interface
------------------------------
@@ -5802,8 +5676,6 @@ by filling up a dict with keys that contain the method names of
interest. On success, these will be filled in with the actual methods.
See the Wic implementation for examples and details.
-.. _wic-usage-examples:
-
Wic Examples
------------
@@ -5813,8 +5685,6 @@ utility. All the examples assume the list of requirements in the
examples assume the previously generated image is
``core-image-minimal``.
-.. _generate-an-image-using-a-provided-kickstart-file:
-
Generate an Image using an Existing Kickstart File
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -6495,8 +6365,6 @@ Changing the listed common targets is as easy as editing your version of
``conf-notes.txt`` in your custom template configuration directory and
making sure you have ``TEMPLATECONF`` set to your directory.
-.. _dev-saving-memory-during-a-build:
-
Conserving Disk Space During Builds
===================================
@@ -6573,8 +6441,6 @@ Yocto Project Reference Manual's glossary chapter.
prevent the installation of a package whose presence is required by
an installed package.
-.. _incrementing-a-binary-package-version:
-
Incrementing a Package Version
------------------------------
@@ -6777,8 +6643,6 @@ Guidelines <https://www.debian.org/doc/debian-policy/ch-controlfields.html>`__.
These guidelines define how versions are compared and what "increasing"
a version means.
-.. _automatically-incrementing-a-binary-package-revision-number:
-
Automatically Incrementing a Package Version Number
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -7077,8 +6941,6 @@ use of runtime package management, you need to do a couple things above
and beyond the basics. The remainder of this section describes what you
need to do.
-.. _runtime-package-management-build:
-
Build Considerations
~~~~~~~~~~~~~~~~~~~~
@@ -7165,8 +7027,6 @@ When your build is complete, your packages reside in the
``tmp`` and your selected package type is RPM, then your RPM packages
are available in ``tmp/deploy/rpm``.
-.. _runtime-package-management-server:
-
Host or Server Machine Setup
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -7193,16 +7053,12 @@ setting of "package_rpm":
$ cd ~/poky/build/tmp/deploy/rpm
$ python3 -m http.server
-.. _runtime-package-management-target:
-
Target Setup
~~~~~~~~~~~~
Setting up the target differs depending on the package management
system. This section provides information for RPM, IPK, and DEB.
-.. _runtime-package-management-target-rpm:
-
Using RPM
^^^^^^^^^
@@ -7283,8 +7139,6 @@ upgrade packages from the specified repository or repositories.
See the `DNF documentation <https://dnf.readthedocs.io/en/latest/>`__ for
additional information.
-.. _runtime-package-management-target-ipk:
-
Using IPK
^^^^^^^^^
@@ -7325,8 +7179,6 @@ repository information:
The ``opkg`` application is now able to find, install, and upgrade packages
from the specified repository.
-.. _runtime-package-management-target-deb:
-
Using DEB
^^^^^^^^^
@@ -7583,8 +7435,6 @@ method.
Additionally, some requirements and caveats exist.
-.. _npm-package-creation-requirements:
-
Requirements and Caveats
~~~~~~~~~~~~~~~~~~~~~~~~
@@ -7619,8 +7469,6 @@ NPM packages:
useful to have NPM on your target. The NPM package name is
``nodejs-npm``.
-.. _npm-using-the-registry-modules-method:
-
Using the Registry Modules Method
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -7731,8 +7579,6 @@ go to ``http://192.168.7.2:3000`` and you see the following:
You can find the recipe in ``workspace/recipes/cute-files``. You can use
the recipe in any layer you choose.
-.. _npm-using-the-npm-projects-method:
-
Using the NPM Projects Code Method
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -7956,8 +7802,6 @@ image cannot use this package group. However, it can install SysVinit
and the appropriate packages will have support for both systemd and
SysVinit.
-.. _selecting-dev-manager:
-
Selecting a Device Manager
==========================
@@ -7974,8 +7818,6 @@ The Yocto Project provides multiple ways to manage the device manager
configuration of device nodes is done in user space by a device
manager like ``udev`` or ``busybox-mdev``.
-.. _static-dev-management:
-
Using Persistent and Pre-Populated\ ``/dev``
--------------------------------------------
@@ -8002,8 +7844,6 @@ If you do not define the ``IMAGE_DEVICE_TABLES`` variable, the default
The population is handled by the ``makedevs`` utility during image
creation:
-.. _devtmpfs-dev-management:
-
Using ``devtmpfs`` and a Device Manager
---------------------------------------
@@ -8036,8 +7876,6 @@ your ``local.conf`` configuration file:
# VIRTUAL-RUNTIME_dev_manager = "busybox-mdev"
# VIRTUAL-RUNTIME_dev_manager = "systemd"
-.. _platdev-appdev-srcrev:
-
Using an External SCM
=====================
@@ -8628,8 +8466,6 @@ hardware, you have to take different steps to enable the tests. See the
following subsections for information on how to enable both types of
tests.
-.. _qemu-image-enabling-tests:
-
Enabling Runtime Tests on QEMU
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -8714,8 +8550,6 @@ Once you start running the tests, the following happens:
You can find the output from the ``unittest`` in the task log at
``${WORKDIR}/temp/log.do_testimage``.
-.. _hardware-image-enabling-tests:
-
Enabling Runtime Tests on Hardware
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -8931,8 +8765,6 @@ wrapper, simply prefix the terminal command with
TEST_SERIALCONTROL_CMD = "${COREBASE}/scripts/contrib/serdevtry picocom -b 115200 /dev/ttyUSB0"
-.. _qemu-image-running-tests:
-
Running Tests
-------------
@@ -9077,8 +8909,6 @@ the build environment using the following:
$ cd tmp/testexport/core-image-sato
$ ./runexported.py testdata.json
-.. _qemu-image-writing-new-tests:
-
Writing New Tests
-----------------
@@ -9110,8 +8940,6 @@ You will notice that all test classes inherit ``oeRuntimeTest``, which
is found in ``meta/lib/oetest.py``. This base class offers some helper
attributes, which are described in the following sections:
-.. _qemu-image-writing-tests-class-methods:
-
Class Methods
~~~~~~~~~~~~~
@@ -9125,8 +8953,6 @@ Class methods are as follows:
:term:`IMAGE_FEATURES` or
:term:`DISTRO_FEATURES`.
-.. _qemu-image-writing-tests-class-attributes:
-
Class Attributes
~~~~~~~~~~~~~~~~
@@ -9174,8 +9000,6 @@ Class attributes are as follows:
- *copy_from(remotepath, localpath):*
``scp root@host:remotepath localpath``.
-.. _qemu-image-writing-tests-instance-attributes:
-
Instance Attributes
~~~~~~~~~~~~~~~~~~~
@@ -9241,8 +9065,6 @@ Once the test is complete, the packages are removed from the DUT.
]
}
-.. _usingpoky-debugging-tools-and-techniques:
-
Debugging Tools and Techniques
==============================
@@ -9333,8 +9155,6 @@ section:
- "`Other Debugging Tips <#dev-other-debugging-others>`__" describes
miscellaneous debugging tips that can be useful.
-.. _dev-debugging-viewing-logs-from-failed-tasks:
-
Viewing Logs from Failed Tasks
------------------------------
@@ -9354,8 +9174,6 @@ links to ``log.do_``\ `taskname`\ ``.``\ `pid` and
when it ran. The symlinks always point to the files corresponding to the
most recent run.
-.. _dev-debugging-viewing-variable-values:
-
Viewing Variable Values
-----------------------
@@ -9477,8 +9295,6 @@ facility:
$ oe-pkgdata-util --help
$ oe-pkgdata-util subcommand --help
-.. _dev-viewing-dependencies-between-recipes-and-tasks:
-
Viewing Dependencies Between Recipes and Tasks
----------------------------------------------
@@ -9545,8 +9361,6 @@ This command
displays a GUI window from which you can view build-time and runtime
dependencies for the recipes involved in building recipename.
-.. _dev-viewing-task-variable-dependencies:
-
Viewing Task Variable Dependencies
----------------------------------
@@ -9638,8 +9452,6 @@ Using BitBake with either of these options causes BitBake to dump out
``sigdata`` files in the ``stamps`` directory for every task it would
have executed instead of building the specified target package.
-.. _dev-viewing-metadata-used-to-create-the-input-signature-of-a-shared-state-task:
-
Viewing Metadata Used to Create the Input Signature of a Shared State Task
--------------------------------------------------------------------------
@@ -9655,8 +9467,6 @@ For conceptual information on shared state, see the
":ref:`overview-manual/overview-manual-concepts:shared state`"
section in the Yocto Project Overview and Concepts Manual.
-.. _dev-invalidating-shared-state-to-force-a-task-to-run:
-
Invalidating Shared State to Force a Task to Run
------------------------------------------------
@@ -9703,8 +9513,6 @@ the build system to run the task again.
shared state, see this
:yocto_git:`commit </cgit.cgi/poky/commit/meta/classes/package.bbclass?id=737f8bbb4f27b4837047cb9b4fbfe01dfde36d54>`.
-.. _dev-debugging-taskrunning:
-
Running Specific Tasks
----------------------
@@ -9812,8 +9620,6 @@ You can view a list of tasks in a given package by running the
The results appear as output to the console and are also in
the file ``${WORKDIR}/temp/log.do_listtasks``.
-.. _dev-debugging-bitbake:
-
General BitBake Problems
------------------------
@@ -9827,8 +9633,6 @@ chose a certain version of a package or why BitBake picked a certain
provider. This command could also help you in a situation where you
think BitBake did something unexpected.
-.. _dev-debugging-buildfile:
-
Building with No Dependencies
-----------------------------
@@ -10190,8 +9994,6 @@ problem is taken care of at its source. See the "`Submitting a Change to
the Yocto Project <#how-to-submit-a-change>`__" section for more
information.
-.. _platdev-gdb-remotedebug:
-
Debugging With the GNU Project Debugger (GDB) Remotely
------------------------------------------------------
@@ -10453,8 +10255,6 @@ To support this kind of debugging, you need do the following:
Consider that this will reduce the application's performance and is
recommended only for debugging purposes.
-.. _dev-other-debugging-others:
-
Other Debugging Tips
--------------------
@@ -10596,8 +10396,6 @@ categorization, progress, or comments on the bug result in Bugzilla
sending you an automated email concerning the particular change or
progress to the bug.
-.. _how-to-submit-a-change:
-
Submitting a Change to the Yocto Project
----------------------------------------
@@ -10691,8 +10489,6 @@ layers you are contributing to.
The following sections provide procedures for submitting a change.
-.. _preparing-changes-for-submissions:
-
Preparing Changes for Submission
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -10776,8 +10572,6 @@ Preparing Changes for Submission
detailed description of change
-.. _submitting-a-patch:
-
Using Email to Submit a Patch
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -10868,8 +10662,6 @@ reduce the burden of patch review on maintainers.
Asking about the status of a patch or change is reasonable if the change
has been idle for a while with no feedback.
-.. _pushing-a-change-upstream:
-
Using Scripts to Push a Change Upstream and Request a Pull
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -11077,8 +10869,6 @@ licensing text and covers how to maintain open source license compliance
during your project's lifecycle. The section also describes how to
enable commercially licensed recipes, which by default are disabled.
-.. _usingpoky-configuring-LIC_FILES_CHKSUM:
-
Tracking License Changes
------------------------
@@ -11089,8 +10879,6 @@ variable tracks changes to the license text. The checksums are validated
at the end of the configure step, and if the checksums do not match, the
build will fail.
-.. _usingpoky-specifying-LIC_FILES_CHKSUM:
-
Specifying the ``LIC_FILES_CHKSUM`` Variable
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -11134,8 +10922,6 @@ five through 16 as license text. The second line refers to a file in
Note that ``LIC_FILES_CHKSUM`` variable is mandatory for all recipes,
unless the ``LICENSE`` variable is set to "CLOSED".
-.. _usingpoky-LIC_FILES_CHKSUM-explanation-of-syntax:
-
Explanation of Syntax
~~~~~~~~~~~~~~~~~~~~~
@@ -11704,8 +11490,6 @@ If you want to set up your own error reporting server, you can obtain
the code from the Git repository at :yocto_git:`/cgit/cgit.cgi/error-report-web/`.
Instructions on how to set it up are in the README document.
-.. _dev-using-wayland-and-weston:
-
Using Wayland and Weston
========================
@@ -11748,8 +11532,6 @@ Enabling Wayland in an Image
To enable Wayland, you need to enable it to be built and enable it to be
included (installed) in the image.
-.. _enable-building:
-
Building Wayland
~~~~~~~~~~~~~~~~
@@ -11768,8 +11550,6 @@ statement in your ``local.conf`` file:
If X11 has been enabled elsewhere, Weston will build Wayland with X11
support
-.. _enable-installation-in-an-image:
-
Installing Wayland and Weston
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
diff --git a/documentation/dev-manual/dev-manual-intro.rst b/documentation/dev-manual/dev-manual-intro.rst
index 05136f735..9bbac9610 100644
--- a/documentation/dev-manual/dev-manual-intro.rst
+++ b/documentation/dev-manual/dev-manual-intro.rst
@@ -4,8 +4,6 @@
The Yocto Project Development Tasks Manual
******************************************
-.. _dev-welcome:
-
Welcome
=======
diff --git a/documentation/dev-manual/dev-manual-qemu.rst b/documentation/dev-manual/dev-manual-qemu.rst
index 63640411d..4e58fc1b6 100644
--- a/documentation/dev-manual/dev-manual-qemu.rst
+++ b/documentation/dev-manual/dev-manual-qemu.rst
@@ -10,8 +10,6 @@ This chapter provides both procedures that show you how to use the Quick
EMUlator (QEMU) and other QEMU information helpful for development
purposes.
-.. _qemu-dev-overview:
-
Overview
========
@@ -39,8 +37,6 @@ following references:
- `Documentation <https://wiki.qemu.org/Manual>`__\ *:* The QEMU user
manual.
-.. _qemu-running-qemu:
-
Running QEMU
============
@@ -187,8 +183,6 @@ allow input of absolute coordinates. This default means that the mouse
can enter and leave the main window without the grab taking effect
leading to a better user experience.
-.. _qemu-running-under-a-network-file-system-nfs-server:
-
Running Under a Network File System (NFS) Server
================================================
@@ -243,8 +237,6 @@ using an NFS server.
runqemu-export-rootfs restart file-system-location
-.. _qemu-kvm-cpu-compatibility:
-
QEMU CPU Compatibility Under KVM
================================
@@ -266,8 +258,6 @@ directory. This setting specifies a ``-cpu`` option passed into QEMU in
the ``runqemu`` script. Running ``qemu -cpu help`` returns a list of
available supported CPU types.
-.. _qemu-dev-performance:
-
QEMU Performance
================
@@ -320,8 +310,6 @@ present, the toolchain is also automatically used.
Server <#qemu-running-under-a-network-file-system-nfs-server>`__"
section for more information.
-.. _qemu-dev-command-line-syntax:
-
QEMU Command-Line Syntax
========================
@@ -377,8 +365,6 @@ Following is the command-line help output for the ``runqemu`` command:
runqemu path/to/<image>-<machine>.wic
runqemu path/to/<image>-<machine>.wic.vmdk
-.. _qemu-dev-runqemu-command-line-options:
-
``runqemu`` Command-Line Options
================================
diff --git a/documentation/dev-manual/dev-manual-start.rst b/documentation/dev-manual/dev-manual-start.rst
index a85b86fbf..f768f092b 100644
--- a/documentation/dev-manual/dev-manual-start.rst
+++ b/documentation/dev-manual/dev-manual-start.rst
@@ -11,8 +11,6 @@ host <dev-manual/dev-manual-start:preparing the build host>`, how to locate
Yocto Project source repositories, and how to create local Git
repositories.
-.. _usingpoky-changes-collaborate:
-
Creating a Team Development Environment
=======================================
@@ -261,8 +259,6 @@ particular working environment and set of practices.
of the available mailing lists, see the ":ref:`resources-mailinglist`" section in
the Yocto Project Reference Manual.
-.. _dev-preparing-the-build-host:
-
Preparing the Build Host
========================
@@ -352,8 +348,6 @@ Kit (eSDK) manual. If you want to work on the kernel, see the :doc:`../kernel-de
Toaster, see the ":doc:`../toaster-manual/toaster-manual-setup-and-use`"
section in the Toaster User Manual.
-.. _setting-up-to-use-crops:
-
Setting Up to Use CROss PlatformS (CROPS)
-----------------------------------------
@@ -454,8 +448,6 @@ Kit (eSDK) manual. If you are going to use the Toaster container, see
the ":doc:`../toaster-manual/toaster-manual-setup-and-use`"
section in the Toaster User Manual.
-.. _setting-up-to-use-wsl:
-
Setting Up to Use Windows Subsystem For Linux (WSLv2)
-----------------------------------------------------
@@ -855,8 +847,6 @@ and then specifically check out that development branch.
master
* &DISTRO_NAME_NO_CAP;
-.. _checkout-out-by-tag-in-poky:
-
Checking Out by Tag in Poky
---------------------------
--
2.29.2
^ permalink raw reply related [flat|nested] 8+ messages in thread
end of thread, other threads:[~2020-11-26 9:48 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-26 9:48 [PATCH 0/7] A second pass at removing labels Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 1/7] sphinx: replace bitbake labels with references to corresponding title Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 2/7] brief-yoctoprojectqs: replace labels with references to section title Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 3/7] dev-manual: " Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 4/7] ref-manual: " Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 5/7] sdk-manual: " Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 6/7] overview-manual: remove unused labels Nicolas Dechesne
2020-11-26 9:48 ` [PATCH 7/7] dev-manual: " Nicolas Dechesne
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.