Lines Matching full:tasks
37 ":ref:`dev-manual/common-tasks:understanding and creating layers`"
38 section of the Yocto Project Development Tasks Manual.
52 a list of tasks from it, and then executing those tasks.
80 BitBake also tries to execute any dependent tasks first. So for example,
152 ":ref:`dev-manual/common-tasks:understanding and creating layers`"
153 section of the Yocto Project Development Tasks Manual.
311 ":ref:`dev-manual/common-tasks:enabling your layer`"
312 section in the Yocto Project Development Tasks Manual.
411 ":ref:`dev-manual/common-tasks:creating your own layer`"
413 Yocto Project Development Tasks Manual. For a general discussion on
585 :ref:`ref-tasks-fetch` task inside
667 :ref:`do_package_write_* <ref-tasks-package_write_deb>`
668 tasks to generate packages and place them into the package holding area
670 ":ref:`ref-tasks-package_write_deb`",
671 ":ref:`ref-tasks-package_write_ipk`",
672 ":ref:`ref-tasks-package_write_rpm`",
674 ":ref:`ref-tasks-package_write_tar`"
707 The :ref:`ref-tasks-fetch` and
708 :ref:`ref-tasks-unpack` tasks fetch
723 task and all tasks that depend on it are re-executed.
795 The :ref:`ref-tasks-patch` task uses a
803 :ref:`ref-tasks-patch` task for more
817 ":ref:`dev-manual/common-tasks:patching code`"
819 Yocto Project Development Tasks Manual. You can also see the
829 After source code is patched, BitBake executes tasks that configure and
836 This step in the build process consists of the following tasks:
838 - :ref:`ref-tasks-prepare_recipe_sysroot`:
844 :ref:`ref-tasks-populate_sysroot`
845 tasks of the recipes on which the recipe containing the tasks
856 :ref:`ref-tasks-configure` task
872 :ref:`ref-tasks-compile` task.
879 :ref:`ref-tasks-install` task.
894 The :ref:`ref-tasks-package` and
895 :ref:`ref-tasks-packagedata`
896 tasks combine to analyze the files found in the
905 :ref:`ref-tasks-populate_sysroot`
907 :ref:`ref-tasks-install` task into
949 :ref:`do_package_write_* <ref-tasks-package_write_deb>`
974 several tasks and variables. The
975 :ref:`ref-tasks-rootfs` task creates
1018 :ref:`read-only root filesystem <dev-manual/common-tasks:creating a read-only root filesystem>`,
1040 through the :ref:`ref-tasks-image`
1047 The build system dynamically creates ``do_image_*`` tasks as needed,
1068 :ref:`do_image_complete <ref-tasks-image-complete>`
1103 :ref:`ref-tasks-populate_sdk`
1105 :ref:`ref-tasks-populate_sdk_ext`
1106 tasks use these key variables to help create the list of packages to
1123 Regardless of the type of SDK being constructed, the tasks perform some
1129 Stamp Files and the Rerunning of Tasks
1155 ":ref:`overview-manual/concepts:setscene tasks and shared state`" section.
1157 tasks that can be accelerated through the sstate cache.
1168 :term:`TMPDIR` will also remove :term:`STAMPS_DIR`, which means tasks will
1177 ":ref:`dev-manual/common-tasks:viewing task variable dependencies`"
1178 section in the Yocto Project Development Tasks Manual.
1180 Setscene Tasks and Shared State
1183 The description of tasks so far assumes that BitBake needs to build
1185 skipping tasks if prebuilt objects are available. These objects are
1201 :ref:`do_package_write_* <ref-tasks-package_write_deb>`
1203 :ref:`ref-tasks-patch` task or a
1204 :ref:`ref-tasks-unpack` task) since
1207 In the build system, the common tasks that have setscene variants are
1208 :ref:`ref-tasks-package`,
1210 :ref:`ref-tasks-deploy`,
1211 :ref:`ref-tasks-packagedata`, and
1212 :ref:`ref-tasks-populate_sysroot`.
1213 Notice that these tasks represent most of the tasks whose output is an
1216 The build system has knowledge of the relationship between these tasks
1217 and other preceding tasks. For example, if BitBake runs
1220 ``do_configure``, ``do_compile``, and ``do_install`` tasks. However, if
1221 ``do_package`` needs to be run, BitBake needs to run those other tasks.
1592 shared state (sstate) code tracks which tasks add which output to the
1606 …information, see the ":ref:`dev-manual/common-tasks:automatically incrementing a package version n…
1607 section in the Yocto Project Development Tasks Manual.
1612 …":ref:`dev-manual/common-tasks:viewing metadata used to create the input signature of a shared sta…
1614 ":ref:`dev-manual/common-tasks:invalidating shared state to force a task to run`"
1615 sections both in the Yocto Project Development Tasks Manual.
1628 :ref:`ref-tasks-install` and
1629 :ref:`ref-tasks-package` task outputs
1634 specific tasks. This methodology does not scale well and does not allow
1635 users to easily add new tasks in layers or as external recipes without
1644 to detect all the inputs to a given task. For shell tasks, this turns
1673 So far, there are solutions for shell scripts. What about Python tasks? The
1674 same approach applies even though these tasks are more difficult. The
1713 tasks on which the particular task depends. Choosing which dependencies
1734 The rules for deciding which hashes of dependent tasks to include
1750 files <overview-manual/concepts:stamp files and the rerunning of tasks>`. This
1786 :ref:`ref-tasks-install` or
1787 :ref:`ref-tasks-package`. The other
1794 :ref:`ref-tasks-deploy` example taken
1815 :ref:`ref-tasks-deploy` task.
1872 file <overview-manual/concepts:stamp files and the rerunning of tasks>`. In
1918 The build processes use the ``*_setscene`` tasks for the task
1920 execution code and tries to accelerate any tasks for which it can find
1923 tasks on which it is dependent are not executed.
1927 :ref:`ref-tasks-package_write_ipk`
1928 tasks would have their shared state packages fetched and extracted.
1937 The above section explained how BitBake skips the execution of tasks
1951 causing the task to re-execute. The task hashes of tasks depending on this
1955 - The *output hash*, a new hash computed from the output of Shared State tasks,
1956 tasks that save their resulting output to a Shared State tarball.
1981 Thanks to this, the depending tasks will keep a previously recorded
1984 output of further downstream tasks can also be retrieved from Shared
1989 The depending tasks, still having a new task hash because of the
1991 to the depending tasks.
1994 tasks in BitBake's run queue doesn't have to propagate to all the
1995 downstream tasks that depend on the output of this task, causing a
1996 full rebuild of such tasks, and so on with the next depending tasks.
2015 their new binaries should remain identical. The corresponding tasks should
2020 - Native tool updates. Though the depending tasks should be rebuilt,
2079 :ref:`ref-tasks-package` task of
2087 :ref:`ref-tasks-packagedata`
2167 Some tasks are easier to implement when allowed to perform certain
2169 :ref:`ref-tasks-install`,
2170 :ref:`do_package_write* <ref-tasks-package_write_deb>`,
2171 :ref:`ref-tasks-rootfs`, and
2172 :ref:`do_image* <ref-tasks-image>`). For example,
2176 One approach to allowing tasks to perform root-only operations would be
2179 approach that is actually used is to run tasks that benefit from root
2187 The capability to run tasks in a fake root environment is known as
2201 memory gives persistence between tasks and builds, which is not