BitBake uses execution units, which are in essence a set of clustered instructions that run in sequence. These units are known as tasks. There are many tasks being scheduled, executed, and checked by BitBake during every recipe's build, provided by classes to form the framework that we use to build a recipe. It is important to understand some of these as we often use, extend, implement, or replace them ourselves when writing a recipe.
Run the following command:
$ bitbake <recipe>BitBake runs a set of scheduled tasks. When we wish to run a specific task, we can use the following command:
$ bitbake <recipe> -c <task>To list the tasks defined for a recipe, we can use the following command:
$ bitbake <recipe> -c listtasksWe will briefly describe each of these here:
do_fetch: The first step when building a recipe is fetching the required source. This is done using the fetching backends feature we discussed previously in this chapter. It is important...