image_populate_mfgtool: Document the MFGTOOLCONFIG parse loop

The loop enumerates the varflags of MFGTOOLCONFIG, which BitBake has no
declarative syntax for, and it feeds do_populate_mfgtool[depends], which
must be set before the task graph is built. Computing the two values with
an inline ${@...} would move the flag validation into expansion, where it
no longer fails the parse. OE-core parses PACKAGECONFIG the same way.

Signed-off-by: Luciano Dittgen <luciano.dittgen@ossystems.com.br>

1 files changed, 3 insertions, 0 deletions

diff --git a/classes/image_populate_mfgtool.bbclass b/classes/image_populate_mfgtool.bbclass
index 43f5fd704..ee3d52226 100644
--- a/classes/image_populate_mfgtool.bbclass
+++ b/classes/image_populate_mfgtool.bbclass
@@ -59,6 +59,9 @@ do_populate_mfgtool[dirs] += "${DEPLOY_DIR_IMAGE} ${WORKDIR}"
 do_populate_mfgtool[recrdeptask] += "do_deploy"
 do_populate_mfgtool[depends] += "uuu-bin:do_populate_sysroot"
 
+# MFGTOOLCONFIG is parsed like PACKAGECONFIG: BitBake cannot enumerate varflags
+# declaratively, and do_populate_mfgtool[depends] must exist before the task graph.
+# nooelint: oelint.task.noanonpython
 python () {
     depends = []
     deploy_files = ""