MIRRORS/poky
1
0
Fork 0
mirror of git://git.yoctoproject.org/poky.git synced 2025-07-19 12:59:02 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity

ref-manual: correct references to WORKDIR to account for recent do_unpack changes

Browse Source 
(From yocto-docs rev: 2e83260484c102fe7b788585cbdd7ca91ba91d85)

Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Alexander Kanavin 2025-06-23 14:42:56 +02:00 committed by Richard Purdie
parent 5ebf08ad8d
commit 73ecebe8a6
2 changed files with 4 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/ref-manual/structure.rst
View File

@ -611,7 +611,7 @@ example, consider ``linux-yocto-kernel-3.0`` on the machine ``qemux86``
built within the Yocto Project. For this package, a work directory of built within the Yocto Project. For this package, a work directory of
``tmp/work/qemux86-poky-linux/linux-yocto/3.0+git1+<.....>``, referred ``tmp/work/qemux86-poky-linux/linux-yocto/3.0+git1+<.....>``, referred
to as the :term:`WORKDIR`, is created. Within this directory, the source is to as the :term:`WORKDIR`, is created. Within this directory, the source is
unpacked to ``linux-qemux86-standard-build`` and then patched by Quilt. unpacked to ``sources/linux-qemux86-standard-build`` and then patched by Quilt.
(See the ":ref:`dev-manual/quilt:using quilt in your workflow`" section in (See the ":ref:`dev-manual/quilt:using quilt in your workflow`" section in
the Yocto Project Development Tasks Manual for more information.) Within the Yocto Project Development Tasks Manual for more information.) Within
the ``linux-qemux86-standard-build`` directory, standard Quilt the ``linux-qemux86-standard-build`` directory, standard Quilt

16
documentation/ref-manual/variables.rst
View File

@ -265,7 +265,7 @@ system and gives an overview of their function and contents.
build process. By default, this directory is the same as the build process. By default, this directory is the same as the
:term:`S` directory, which is defined as:: :term:`S` directory, which is defined as::
S = "${WORKDIR}/${BP}" S = "${UNPACKDIR}/${BP}"
You can separate the (:term:`S`) directory and the directory pointed to You can separate the (:term:`S`) directory and the directory pointed to
by the :term:`B` variable. Most Autotools-based recipes support by the :term:`B` variable. Most Autotools-based recipes support
@ -8060,7 +8060,7 @@ system and gives an overview of their function and contents.
:term:`S` :term:`S`
The location in the :term:`Build Directory` where The location in the :term:`Build Directory` where
unpacked recipe source code resides. By default, this directory is unpacked recipe source code resides. By default, this directory is
``${``\ :term:`WORKDIR`\ ``}/${``\ :term:`BPN`\ ``}-${``\ :term:`PV`\ ``}``, ``${``\ :term:`UNPACKDIR`\ ``}/${``\ :term:`BPN`\ ``}-${``\ :term:`PV`\ ``}``,
where ``${BPN}`` is the base recipe name and ``${PV}`` is the recipe where ``${BPN}`` is the base recipe name and ``${PV}`` is the recipe
version. If the source tarball extracts the code to a directory named version. If the source tarball extracts the code to a directory named
anything other than ``${BPN}-${PV}``, or if the source code is anything other than ``${BPN}-${PV}``, or if the source code is
@ -8073,19 +8073,10 @@ system and gives an overview of their function and contents.
``poky/build``. In this case, the work directory the build system ``poky/build``. In this case, the work directory the build system
uses to keep the unpacked recipe for ``db`` is the following:: uses to keep the unpacked recipe for ``db`` is the following::
poky/build/tmp/work/qemux86-poky-linux/db/5.1.19-r3/db-5.1.19 poky/build/tmp/work/qemux86-poky-linux/db/5.1.19-r3/sources/db-5.1.19
The unpacked source code resides in the ``db-5.1.19`` folder. The unpacked source code resides in the ``db-5.1.19`` folder.
This next example assumes a Git repository. By default, Git
repositories are cloned to ``${WORKDIR}/git`` during
:ref:`ref-tasks-fetch`. Since this path is different
from the default value of :term:`S`, you must set it specifically so the
source can be located::
SRC_URI = "git://path/to/repo.git;branch=main"
S = "${WORKDIR}/git"
:term:`SANITY_REQUIRED_UTILITIES` :term:`SANITY_REQUIRED_UTILITIES`
Specifies a list of command-line utilities that should be checked for Specifies a list of command-line utilities that should be checked for
during the initial sanity checking process when running BitBake. If during the initial sanity checking process when running BitBake. If
@ -8460,7 +8451,6 @@ system and gives an overview of their function and contents.
sources are fetched from a Git repository and ``setup.py`` is in a sources are fetched from a Git repository and ``setup.py`` is in a
``python/pythonmodule`` subdirectory, you would have this:: ``python/pythonmodule`` subdirectory, you would have this::
S = "${WORKDIR}/git"
SETUPTOOLS_SETUP_PATH = "${S}/python/pythonmodule" SETUPTOOLS_SETUP_PATH = "${S}/python/pythonmodule"
:term:`SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS` :term:`SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS`