documentation/ref-manual/tasks.rst

17 ":ref:`bitbake:bitbake-user-manual/bitbake-user-manual-metadata:tasks`" and
18 ":ref:`bitbake:bitbake-user-manual/bitbake-user-manual-execution:dependencies`" sections in the
81 :ref:`deploy <ref-classes-deploy>` class and should write the output
83 confused with ``${DEPLOY_DIR}``. The :ref:`deploy <ref-classes-deploy>` class sets up
95 after :ref:`ref-tasks-compile`, you can add it by doing
105 … (though it is harmless), because the :ref:`base <ref-classes-base>` class contains the following::
110    See the ":ref:`bitbake-user-manual/bitbake-user-manual-execution:dependencies`"
123 determine the correct :ref:`fetcher <bitbake:bitbake-user-manual/bitbake-user-manual-fetching:fetch…
133 :ref:`ref-tasks-rootfs` task during which packages are
141 For more information on image creation, see the ":ref:`overview-manual/concepts:image generation`"
151 :ref:`ref-tasks-image` task during which image
160 ":ref:`overview-manual/concepts:image generation`"
173 :ref:`ref-tasks-package`, ``do_package_write_*``, and
174 :ref:`ref-tasks-rootfs`), run under
175 :ref:`fakeroot <overview-manual/concepts:fakeroot and pseudo>`.
216 :ref:`ref-tasks-packagedata` task, also saves some
219 ":ref:`overview-manual/concepts:automatically added runtime dependencies`"
228 see the :ref:`insane <ref-classes-insane>` class.
238 ":ref:`overview-manual/concepts:package feeds`" section in
249 ":ref:`overview-manual/concepts:package feeds`" section in
260 ":ref:`overview-manual/concepts:package feeds`" section in
271 ":ref:`overview-manual/concepts:package feeds`" section in
280 :ref:`ref-tasks-package` task in
344 ":ref:`overview-manual/concepts:patching`" section in
346 ":ref:`dev-manual/common-tasks:patching code`" section in the
363 ":ref:`overview-manual/concepts:sdk generation`"
373 SDK (eSDK). See the ":ref:`overview-manual/concepts:sdk generation`"
384 :ref:`ref-tasks-install` task into the appropriate
409 ":ref:`staging <ref-classes-staging>`" class for more information.
418 ":ref:`ref-classes-rm-work`" section.
429 ":ref:`overview-manual/concepts:source fetching`"
450 :ref:`ref-tasks-unpack` task forward (i.e. ``do_unpack``,
451 :ref:`ref-tasks-configure`,
452 :ref:`ref-tasks-compile`,
453 :ref:`ref-tasks-install`, and
454 :ref:`ref-tasks-package`).
461 :ref:`sstate <overview-manual/concepts:shared state cache>` cache files.
465 use the :ref:`ref-tasks-cleansstate` task instead
474 (:ref:`sstate <overview-manual/concepts:shared state cache>`) cache, and
477 identical to the :ref:`ref-tasks-cleansstate` task
485 if you want to start fresh with the :ref:`ref-tasks-fetch`
494 (:ref:`sstate <overview-manual/concepts:shared state cache>`) cache for a
496 :ref:`ref-tasks-clean` task with the added removal of
497 shared state (:ref:`sstate <overview-manual/concepts:shared state cache>`)
525 functions as if within the BitBake environment. See the ":ref:`dev-manual/common-tasks:using a pyth…
535 or both. See the ":ref:`dev-manual/common-tasks:using a development shell`" section in the
551 Creates or updates the index in the :ref:`overview-manual/concepts:package feeds` area.
589 See the ":ref:`overview-manual/concepts:image generation`"
600 ":ref:`dev-manual/common-tasks:performing automated runtime testing`"
613 ":ref:`dev-manual/common-tasks:performing automated runtime testing`"
620 tasks (e.g. the :ref:`ref-tasks-menuconfig` task) are
640 :ref:`ref-tasks-kernel_configme` task and the
642 (:ref:`ref-tasks-kernel_menuconfig`). Once the
650 ":ref:`kernel-dev/common:creating configuration fragments`"
670 :ref:`ref-tasks-kernel_menuconfig` task. The
680 ":ref:`kernel-dev/common:validating configuration`"
688 After the kernel is patched by the :ref:`ref-tasks-patch`
711 See the ":ref:`kernel-dev/common:using \`\`menuconfig\`\``"
725 :ref:`ref-tasks-patch` and
726 :ref:`ref-tasks-kernel_configme`.
735 ":ref:`kernel-dev/common:using \`\`menuconfig\`\``"
747 :ref:`ref-tasks-kernel_menuconfig` task. You
761 :ref:`ref-tasks-compile_kernelmodules` task