Lines Matching full:tasks

14 execute single tasks, compile single recipe files, capture or clear
94 tasks. See the
100 recipes and tasks that are executed.
218 tasks that the recipe defines and a set of data consisting of keys and
219 values as well as dependency information about the tasks.
361 Each target BitBake builds consists of multiple tasks such as ``fetch``,
384 BitBake can now calculate exactly what tasks it needs to run and in what
386 :ref:`bitbake-user-manual/bitbake-user-manual-execution:executing tasks`
392 variable. BitBake continues to fork threads as long as there are tasks
393 ready to run, those tasks have all their dependencies met, and the
402 does not rerun tasks that are already completed unless a timestamp is
418 flag to make some tasks machine-specific.
422 Some tasks are marked as "nostamp" tasks. No timestamp file is
423 created when these tasks are run. Consequently, "nostamp" tasks are
426 For more information on tasks, see the
427 :ref:`bitbake-user-manual/bitbake-user-manual-metadata:tasks` section.
429 Executing Tasks
432 Tasks can be either a shell task or a Python task. For shell tasks,
442 For Python tasks, BitBake executes the task internally and logs
444 write the functions to files similar to the way shell tasks are handled.
445 Logging will be handled in a way similar to shell tasks as well.
447 The order in which BitBake runs the tasks is controlled by its task
468 to detect all the inputs to a given task. For shell tasks, this turns
491 So far we have solutions for shell scripts. What about Python tasks? The
492 same approach applies even though these tasks are more difficult. The
528 to add the hashes of all the tasks on which the particular task depends.
550 The rules for deciding which hashes of dependent tasks to include
618 given task or set of tasks with the pre-built artifact. BitBake solves
625 running the main tasks.
629 with a list of tasks and corresponding hashes it wants to build. This
630 function is designed to be fast and returns a list of the tasks for
633 Next, for each of the tasks that were returned as possibilities, BitBake