manuals: add references to the "do_build" task

[YOCTO #14508]
(From yocto-docs rev: c8efd2eeb329344c48935f8998e9a689d66348ca)

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reported-by: Quentin Schulz <foss@0leil.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Michael Opdenacker 2022-09-23 17:24:16 +02:00 committed by Richard Purdie
parent 9fece9c361
commit edaa121c7b
2 changed files with 3 additions and 3 deletions

View File

@ -9595,8 +9595,8 @@ Running Specific Tasks
Any given recipe consists of a set of tasks. The standard BitBake
behavior in most cases is: :ref:`ref-tasks-fetch`, ``do_unpack``, ``do_patch``,
``do_configure``, ``do_compile``, :ref:`ref-tasks-install`, ``do_package``,
``do_package_write_*``, and ``do_build``. The default task is
``do_build`` and any tasks on which it depends build first. Some tasks,
``do_package_write_*``, and :ref:`ref-tasks-build`. The default task is
:ref:`ref-tasks-build` and any tasks on which it depends build first. Some tasks,
such as ``do_devshell``, are not part of the default build chain. If you
wish to run a task that is not part of the default build chain, you can
use the ``-c`` option in BitBake. Here is an example::

View File

@ -206,7 +206,7 @@ Package/recipe splitting
Image / SDK generation changes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Recursive dependencies on the ``do_build`` task are now disabled when
- Recursive dependencies on the :ref:`ref-tasks-build` task are now disabled when
building SDKs. These are generally not needed; in the unlikely event
that you do encounter problems then it will probably be as a result of
missing explicit dependencies that need to be added.