linux/meta-freescale.git/dynamic-layers/qt6-layer, branch master

qtbase: Drop the redundant leading space in PACKAGECONFIG_GRAPHICS

2026-09-11T16:59:25+00:00

The line continuation already separates the value from the entries below, and every other multi-line assignment in this bbappend opens with "\ -- imxgpu2d was the lone exception. Validated on imx6slevk, the only i.MX family where imxgpu2d wins the selection: bitbake qtbase with do_configure forced, buildhistory unchanged. Signed-off-by: Luciano Dittgen

qtbase: Scope the wayland PACKAGECONFIG knob to our machines

2026-09-04T12:52:09+00:00

meta-qt6 puts the wayland knob in PACKAGECONFIG_GRAPHICS, which the machine assignments here replace, so commit 25d78fb6b restored it with an unconditional +=. That overrides core behaviour on machines this layer does not own, which fails yocto-check-layer. imx-generic-bsp and qoriq are disjoint and together cover every machine we provide. Built qtbase on imx8mm-lpddr4-evk/fslc-wayland; buildhistory is identical. Signed-off-by: Luciano Dittgen

qtbase: Reformat PACKAGECONFIG_GL/GRAPHICS, drop multilineident override

2026-08-24T18:02:46+00:00

oelint.vars.multilineident flagged PACKAGECONFIG_GL:imxgpu2d (qt5) and PACKAGECONFIG_GRAPHICS:imxgpu2d (qt6). The value used a ' gl' token whose leading space (a PACKAGECONFIG separator inside the string) made the first continuation line count as one column too wide. Per review, move the separator out of the token: use an empty opening quote so BitBake supplies the leading space, and drop the space inside the token ('gl'). Every item is now on an aligned 4-space continuation line, which satisfies the rule without a nooelint directive. PACKAGECONFIG is whitespace-split, so the resolved config list is unchanged. Both files are dynamic-layer bbappends whose trigger layer is not checked out in this tree, so this is argued from the metadata, not measured with buildhistory. Signed-off-by: Luciano Dittgen

oelint: Suppress noncoreoverride on the machine-gated bbappend idiom

2026-08-07T12:30:00+00:00

oelint.vars.noncoreoverride flags every statement in a bbappend that carries no MACHINE or DISTRO override suffix, because an unconditional override of core behaviour fails yocto-check-layer. The check is purely syntactic: it cannot see that a statement's effective value is already machine-gated, which is exactly how most of this layer is written. DRM-REMOVE = "" <- flagged DRM-REMOVE:imxgpu:mx6-nxp-bsp = "drm-gl drm-gles2" PACKAGECONFIG:remove = "${DRM-REMOVE}" <- flagged Neither line can be scoped. A fallback default cannot carry an override for the machines it is the fallback for, and the dispatch line that consumes it is a no-op wherever the helper expands empty. Scoping them anyway would damage correct metadata: weston-init reads HAS_G2D as "elif ${HAS_G2D};" in shell, where an empty value is a syntax error. Suppress the 58 sites proven inert, each with its own rationale. The proof is a bitbake -e comparison on MACHINE=qemuarm64 -- a machine this layer does not own -- with meta-freescale in and out of BBLAYERS. At every suppressed site SRC_URI, DEPENDS, PACKAGECONFIG, OPENGL_PKGCONFIGS and REQUIRED_DISTRO_FEATURES are unchanged; eight recipes show no effective difference at all. The helper variables are defined in the datastore but every consumer is override-scoped. For the 18 FILESEXTRAPATHS sites there is a stronger result: FILESPATH and FILESEXTRAPATHS are both in BB_BASEHASH_IGNORE_VARS, so they cannot reach a task signature. Two anonymous python blocks are deliberately left unsuppressed and explained in place instead. For those, oelint anchors the finding to the line before the block, so a directive placed above only moves the anchor onto itself: the finding survives and inlinesuppress_na is reported for the directive. oelint.task.noanonpython anchors the same block to the 'python' line and suppresses correctly, so the two rules disagree about where the construct starts. Upstream oelint bug candidate. The rule count goes 76 -> 18 and the layer total 548 -> 491. The 16 findings that remain are not noise: they are measured, genuine unconditional changes to machines this layer does not own, and are left open for separate fixes. This change is comment-only; no non-comment line is added or modified. Validated with bitbake -p (1166 recipes, 0 errors) and an authoritative driver rescan showing zero introduced findings in any of the 24 edited files. The residual override/outofcontext churn in the rescan is the known shared-metadata scan non-determinism and nets to zero. Signed-off-by: Luciano Dittgen

global: Use single space around variable assignments

2026-07-12T18:55:50+00:00

meta-freescale used columnar alignment (multiple spaces padding the variable name out to a common column) for tables of assignments such as the fsl-eula-unpack MD5 sums and PACKAGECONFIG[...] entries. The Yocto Recipe Style Guide and oelint-adv (oelint.vars.spacesassignment) call for a single space around the assignment operator. Collapse the padding to a single space on every flagged assignment. The change is purely whitespace around the operator: variable names, operators and values (including whitespace inside quoted values) are untouched, as confirmed by an empty 'git diff -w'. Signed-off-by: Otavio Salvador

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

global: Clean up BitBake list spacing

2026-07-07T17:40:00+00:00

Normalize list continuations, append spacing, quote style, and simple flag values so the metadata follows oelint BitBake syntax expectations. Tested with: git diff --check. Signed-off-by: Luciano Dittgen

qtwayland: extend xcomposite disabling to all i.MX 9 family

2025-12-17T13:25:41+00:00

Use mx9-nxp-bsp override instead of mx95-nxp-bsp to disable xcomposite-egl and xcomposite-glx for the entire i.MX 9 family. Signed-off-by: Vitor Soares

qtwayland: add overrides for i.mx 95

2024-10-24T08:05:24+00:00

Add the relevant configuration for an i.MX 95 SoC. Signed-off-by: Max Krummenacher

qtbase: add overrides for i.mx 95

2024-10-24T08:05:24+00:00

Add the relevant configuration for an i.MX 95 SoC. Signed-off-by: Max Krummenacher