linux/meta-freescale.git/classes/image_populate_mfgtool.bbclass, branch master

Merge pull request #2614 from lucianogdittgen/oelint-cleanup-17

2026-08-04T11:21:59+00:00

oelint: Patch headers, kernel/u-boot SECTION, task docs and install modes

image_populate_mfgtool: use oe.utils.base_set_filespath

2026-08-04T07:59:26+00:00

Commit 4e04ca516c6b ("utils: Move functions from utils.bbclass to utils.py") from openembedded-core moved base_set_filespath into oe.utils. Signed-off-by: Antoine Gouby

classes: Document the custom tasks and helpers per oelint

2026-08-03T19:13:30+00:00

oelint-adv reports 'oelint.task.docstrings: Every custom task should have a doc string set by task[doc] = ...' for the five custom functions in classes/. Doc strings are shown by 'bitbake -c listtasks', so this is useful metadata rather than linter appeasement, and the layer already applies it in fsl-kernel-localversion, fsl-eula-unpack, kernel-imximage and imx-boot-container. The flag has to be keyed on the function name exactly as written, which is why the two image_types_fsl entries are on IMAGE_CMD:uboot-mxsboot-* rather than on the do_image_uboot_mxsboot_* tasks they generate; keying them on the task name does not satisfy the rule. fsl_vivante_kernel_driver_handler is an event handler rather than a task. It is documented here for consistency with the other non-task helpers the layer already documents (__set_insane_skip, update_file), rather than suppressed as machine-overrides-extender does. bitbake never reads the 'doc' flag when computing task checksums -- bb/data.py build_dependencies() only consults vardeps, vardepvalue, vardepsexclude, exports, postfuncs, prefuncs, lineno and filename -- so these additions cannot change a signature or invalidate sstate. Verified by re-linting each file: all five findings are gone and nothing new is reported. Signed-off-by: Luciano Dittgen

global: Drop needless whitespace in assignments

2026-07-12T07:54:14+00:00

Remove the stray space between an assignment's opening quote and its line-continuation backslash, and the space before '%' in inline ${@...} expressions. Generated mechanically by oelint-adv's auto-fix for a single rule (oelint.vars.notneededspace), isolated to one commit. The affected values are whitespace-separated lists (leading space is insignificant) and Python format expressions ("%s"% p is equivalent), so there is no functional change; a re-run of oelint-adv reports the rule clean. Signed-off-by: Otavio Salvador

classes/image_populate_mfgtool: fix basehash value change

2023-04-14T19:10:42+00:00

Signed-off-by: Otavio Salvador

classes/image_populate_mfgtool: avoid error copying duplicated files

2023-04-13T19:50:02+00:00

Eventually, multiple `uuu` script may install same binaries. We need to ensure we install them once, otherwise it'll fail as it might try to override a existing binary. This commit ensure all dependencies and binaries are mentioned once, removing duplication. Fixes: ae7af6f8 ("classes/image_populate_mfgtool: init") Signed-off-by: Otavio Salvador

classes/image_populate_mfgtool: init

2023-04-12T20:12:18+00:00

The class provides the infrastructure for MFGTOOL generation and is tied to images. To generate the bundle, the task populate_mfgtool must be called. For example: ,----[ Running populate_mfgtool for core-image-minimal image ] | $: bitbake core-image-minimal -c populate_mfgtool `---- The class behavior is controlled through the MFGTOOLCONFIG (analogous to PACKAGECONFIG) variable. The MFGTOOLCONFIG variable itself specifies a space-separated list of the script to enable. Following the script, you can determine the behavior of each script by providing up to two order-dependent arguments, which are separated by commas. You can omit any argument you like but must retain the separating commas. The order is important and specifies the following: 1. Extra dependencies that should be added to the do_populate_mfgtool task, if the script is enabled. 2. Extra binaries that should be added to the bundle, if the script is enabled. For example: ,----[ Defining foo.uuu.in and bar.uuu script ] | MFGTOOLCONFIG = "foo.uuu.in bar.uuu" | MFGTOOLCONFIG[foo.uuu.in] = "dep-foo1:do_deploy dep-foo2:do_deploy,file-foo1" | MFGTOOLCONFIG[bar.uuu] = "dep-bar1:do_deploy,file-bar1 file-bar2" `---- The dep-foo1:do_deploy, dep-foo2:do_deploy, and dep-bar1:do_deploy are added to do_populate_mfgtool dependencies. In addition, file-foo1, file-bar1, and file-bar2 are copied to the bundle, only if the script is enabled. During the mfgtool bundle generation, the uuu.in files are processed and some variables replaced. The variables are: - MACHINE - UBOOT_BINARY - SPL_BINARY - IMAGE_BASENAME Signed-off-by: Otavio Salvador