@@ -9,6 +9,35 @@ tasks to complete configuring, compiling, and packaging software. This
chapter provides a reference of the tasks defined in the OpenEmbedded
build system.
+To see the tasks defined (in alphabetical order) for a given recipe,
+you can run:
+
+.. code-block:: console
+
+ $ bitbake -c listtasks recipename
+ do_build Default task for a recipe - depends on all other normal tasks required to 'build' a recipe
+ do_checkuri Validates the SRC_URI value
+ do_clean Removes all output files for a target
+ do_cleanall Removes all output files, shared state cache, and downloaded source files for a target
+ do_cleansstate Removes all output files and shared state cache for a target
+ do_compile Compiles the source in the compilation directory
+ .. etc etc ...
+
+In addition, once a recipe has been built, you can find in that recipe's
+``${WORKDIR}/temp/`` directory not only all of the "run" and "log" files
+for every task executed for that recipe, but a ``log.task_order`` file
+that lists the order of execution of those tasks:
+
+.. code-block:: console
+
+ $ cat log.task_order
+ 20260626-045459.439754 do_fetch (3798706): log.do_fetch.3798706
+ 20260626-045459.805253 do_unpack (3798765): log.do_unpack.3798765
+ 20260626-045501.005518 do_patch (3798918): log.do_patch.3798918
+ 20260626-045501.012781 do_prepare_recipe_sysroot (3798919): log.do_prepare_recipe_sysroot.3798919
+ 20260626-045501.210527 do_populate_lic (3798933): log.do_populate_lic.3798933
+ ... etc etc ...
+
Normal Recipe Build Tasks
=========================
As in done in the "Classes" section, add a couple paragraphs to explain how the developer can examine the tasks for a recipe. Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> ---