mirror of
https://git.yoctoproject.org/poky
synced 2026-01-29 21:08:42 +01:00
sdk-manual: fix broken references
Detected by running: git grep "^[\ ]*\" section" | grep -v "\`" (From yocto-docs rev: 1e4909304a7e04fa707633b58c5e0d68a67d353a) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Reviewed-by: Quentin Schulz <foss@0leil.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
9385815965
commit
7a9b74e9d2
@@ -74,9 +74,9 @@ adjustments:
|
||||
is set using the "?=" operator. Consequently, you will need to
|
||||
either define the entire list by using the "=" operator, or you
|
||||
will need to append a value using either "_append" or the "+="
|
||||
operator. You can learn more about these operators in the "
|
||||
Basic Syntax
|
||||
" section of the BitBake User Manual.
|
||||
operator. You can learn more about these operators in the
|
||||
":ref:`bitbake:bitbake-user-manual/bitbake-user-manual-metadata:basic syntax`"
|
||||
section of the BitBake User Manual.
|
||||
|
||||
.
|
||||
|
||||
@@ -350,9 +350,9 @@ in most cases.
|
||||
If you set
|
||||
SDK_EXT_TYPE
|
||||
to "minimal", then providing a shared state mirror is mandatory so
|
||||
that items can be installed as needed. See the "
|
||||
Providing Additional Installable Extensible SDK Content
|
||||
" section for more information.
|
||||
that items can be installed as needed. See the
|
||||
:ref:`sdk-manual/appendix-customizing:providing additional installable extensible sdk content`
|
||||
section for more information.
|
||||
|
||||
You can explicitly control whether or not to include the toolchain when
|
||||
you build an SDK by setting the
|
||||
|
||||
@@ -15,9 +15,8 @@ hardware, and ease integration into the rest of the
|
||||
.. note::
|
||||
|
||||
For a side-by-side comparison of main features supported for an
|
||||
extensible SDK as compared to a standard SDK, see the "
|
||||
Introduction
|
||||
" section.
|
||||
extensible SDK as compared to a standard SDK, see the
|
||||
:ref:`sdk-manual/intro:introduction` section.
|
||||
|
||||
In addition to the functionality available through ``devtool``, you can
|
||||
alternatively make use of the toolchain directly, for example from
|
||||
@@ -89,9 +88,9 @@ the SDK for ``core-image-sato`` and using the current &DISTRO; snapshot::
|
||||
.. note::
|
||||
|
||||
As an alternative to downloading an SDK, you can build the SDK
|
||||
installer. For information on building the installer, see the "
|
||||
Building an SDK Installer
|
||||
" section.
|
||||
installer. For information on building the installer, see the
|
||||
:ref:`sdk-manual/appendix-obtain:building an sdk installer`
|
||||
section.
|
||||
|
||||
The SDK and toolchains are self-contained and by default are installed
|
||||
into the ``poky_sdk`` folder in your home directory. You can choose to
|
||||
@@ -606,9 +605,9 @@ counterparts.
|
||||
Several methods exist by which you can upgrade recipes -
|
||||
devtool upgrade
|
||||
happens to be one. You can read about all the methods by which you
|
||||
can upgrade recipes in the "
|
||||
Upgrading Recipes
|
||||
" section of the Yocto Project Development Tasks Manual.
|
||||
can upgrade recipes in the
|
||||
:ref:`dev-manual/common-tasks:upgrading recipes` section
|
||||
of the Yocto Project Development Tasks Manual.
|
||||
|
||||
The ``devtool upgrade`` command is flexible enough to allow you to
|
||||
specify source code revision and versioning schemes, extract code into
|
||||
|
||||
@@ -135,9 +135,8 @@ project:
|
||||
|
||||
To learn about environment variables established when you run the
|
||||
cross-toolchain environment setup script and how they are used or
|
||||
overridden when the Makefile, see the "
|
||||
Makefile-Based Projects
|
||||
" section.
|
||||
overridden when the Makefile, see the
|
||||
:ref:`sdk-manual/working-projects:makefile-based projects` section.
|
||||
|
||||
This next command is a simple way to verify the installation of your
|
||||
project. Running the command prints the architecture on which the
|
||||
|
||||
Reference in New Issue
Block a user