@@ -166,7 +166,7 @@ section.
BSPs, which are maintained in their own layers or in layers designed
to contain several BSPs. To get an idea of machine support through
BSP layers, you can look at the
- :yocto_dl:`index of machines </releases/yocto/yocto-&DISTRO;/machines>`
+ :yocto_dl:`index of machines </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines>`
for the release.
#. *Optionally Clone the meta-intel BSP Layer:* If your hardware is
@@ -75,7 +75,7 @@ available. Follow these general steps to run QEMU:
your :term:`Build Directory`.
- If you have not built an image, you can go to the
- :yocto_dl:`machines/qemu </releases/yocto/yocto-&DISTRO;/machines/qemu/>` area and download a
+ :yocto_dl:`machines/qemu </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines/qemu/>` area and download a
pre-built image that matches your architecture and can be run on
QEMU.
@@ -615,7 +615,7 @@ Accessing Source Archives
The Yocto Project also provides source archives of its releases, which
are available on :yocto_dl:`/releases/yocto/`. Then, choose the subdirectory
containing the release you wish to use, for example
-:yocto_dl:`yocto-&DISTRO; </releases/yocto/yocto-&DISTRO;/>`.
+:yocto_dl:`&DISTRO_REL_LATEST_TAG; </releases/yocto/&DISTRO_REL_LATEST_TAG;/>`.
You will find there source archives of individual components (if you wish
to use them individually), and of the corresponding Poky release bundling
@@ -393,7 +393,7 @@ If you would prefer not to use the ``install-buildtools`` script, you can instea
download and run a pre-built :term:`buildtools` installer yourself with the following
steps:
-#. Go to :yocto_dl:`/releases/yocto/yocto-&DISTRO;/buildtools/`, locate and
+#. Go to :yocto_dl:`/releases/yocto/&DISTRO_REL_LATEST_TAG;/buildtools/`, locate and
download the ``.sh`` file corresponding to your host architecture
and to :term:`buildtools`, :term:`buildtools-extended` or :term:`buildtools-make`.
@@ -452,7 +452,7 @@ universal, the list includes them just in case:
the Source Directory, if you do, the top-level directory name of the
Source Directory is derived from the Yocto Project release tarball.
For example, downloading and unpacking poky tarballs from
- :yocto_dl:`/releases/yocto/&DISTRO_REL_TAG;/`
+ :yocto_dl:`/releases/yocto/&DISTRO_REL_LATEST_TAG;/`
results in a Source Directory whose root folder is named poky.
@@ -29,7 +29,7 @@ and then run the script to hand-install the toolchain.
Follow these steps to locate and hand-install the toolchain:
#. *Go to the Installers Directory:* Go to
- :yocto_dl:`/releases/yocto/yocto-&DISTRO;/toolchain/`
+ :yocto_dl:`/releases/yocto/&DISTRO_REL_LATEST_TAG;/toolchain/`
#. *Open the Folder for Your Build Host:* Open the folder that matches
your :term:`Build Host` (i.e.
@@ -201,7 +201,7 @@ Follow these steps to extract the root filesystem:
Image File:* You need to find and download the root filesystem image
file that is appropriate for your target system. These files are kept
in machine-specific folders in the
- :yocto_dl:`Index of Releases </releases/yocto/yocto-&DISTRO;/machines/>`
+ :yocto_dl:`Index of Releases </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines/>`
in the "machines" directory.
The machine-specific folders of the "machines" directory contain
@@ -245,7 +245,7 @@ Follow these steps to extract the root filesystem:
Here is an example command that extracts the root filesystem
from a previously built root filesystem image that was downloaded
- from the :yocto_dl:`Index of Releases </releases/yocto/yocto-&DISTRO;/machines/>`.
+ from the :yocto_dl:`Index of Releases </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines/>`.
This command extracts the root filesystem into the ``core2-64-sato``
directory::
@@ -87,7 +87,7 @@ Host` by running the ``*.sh`` installation script.
You can download a tarball installer, which includes the pre-built
toolchain, the ``runqemu`` script, the internal build system,
``devtool``, and support files from the appropriate
-:yocto_dl:`toolchain </releases/yocto/yocto-&DISTRO;/toolchain/>` directory within the Index of
+:yocto_dl:`toolchain </releases/yocto/&DISTRO_REL_LATEST_TAG;/toolchain/>` directory within the Index of
Releases. Toolchains are available for several 32-bit and 64-bit
architectures with the ``x86_64`` directories, respectively. The
toolchains the Yocto Project provides are based off the
@@ -173,7 +173,7 @@ You just need to follow these general steps:
root filesystem images.
If you are going to develop your application on hardware, go to the
- :yocto_dl:`machines </releases/yocto/yocto-&DISTRO;/machines/>` download area and choose a
+ :yocto_dl:`machines </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines/>` download area and choose a
target machine area from which to download the kernel image and root
filesystem. This download area could have several files in it that
support development using actual hardware. For example, the area
@@ -183,7 +183,7 @@ You just need to follow these general steps:
If you are going to develop your application and then run and test it
using the QEMU emulator, go to the
- :yocto_dl:`machines/qemu </releases/yocto/yocto-&DISTRO;/machines/qemu>` download area. From this
+ :yocto_dl:`machines/qemu </releases/yocto/&DISTRO_REL_LATEST_TAG;/machines/qemu>` download area. From this
area, go down into the directory for your target architecture (e.g.
``qemux86_64`` for an Intel-based 64-bit architecture). Download the
kernel, root filesystem, and any other files you need for your
@@ -43,7 +43,7 @@ Host` by running the ``*.sh`` installation script.
You can download a tarball installer, which includes the pre-built
toolchain, the ``runqemu`` script, and support files from the
-appropriate :yocto_dl:`toolchain </releases/yocto/yocto-&DISTRO;/toolchain/>` directory within
+appropriate :yocto_dl:`toolchain </releases/yocto/&DISTRO_REL_LATEST_TAG;/toolchain/>` directory within
the Index of Releases. Toolchains are available for several 32-bit and
64-bit architectures with the ``x86_64`` directories, respectively. The
toolchains the Yocto Project provides are based off the
After introducing the DISTRO_LATEST_TAG and DISTRO_REL_LATEST_TAG macros, use them in links that currently use DISTRO/DISTRO_REL_TAG. When building for the tip of a branch, this will replace the current A.B.999 in links to the latest existing tag. The links were found across the documentation by running 'grep -r "http.*5\.2\.999"' inside the _build/html output after building the docs. [YOCTO #14802] Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> --- documentation/bsp-guide/bsp.rst | 2 +- documentation/dev-manual/qemu.rst | 2 +- documentation/dev-manual/start.rst | 2 +- documentation/ref-manual/system-requirements.rst | 2 +- documentation/ref-manual/terms.rst | 2 +- documentation/sdk-manual/appendix-obtain.rst | 6 +++--- documentation/sdk-manual/extensible.rst | 2 +- documentation/sdk-manual/intro.rst | 4 ++-- documentation/sdk-manual/using.rst | 2 +- 9 files changed, 12 insertions(+), 12 deletions(-)