You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When this pattern is used across multiple bbappends, it triggers the following false positive: warning:oelint.var.multiinclude:'${PN}_mvista.inc' is included multiple times
This warning highlights two issues: First, it appears that this check operates at the global distro level instead of examining includes per recipe. Second, variables are not expanded, which would correctly resolve into unique include filenames.
The text was updated successfully, but these errors were encountered:
It is true that the include name is not expanded so far, still I don't get how that could result in any sort of warning here.
The linter will group files into logical groups (meaning recipe + matching bbappends), so unless there are multiple bbappends using this scheme that apply to a single recipe, the include statement in question should be parsed only once per group.
Please provide a minimal example on how warning is falsely raised.
Consider meta-montavista-cgx as an example of a pattern where an .inc file is included only when a certain variable is set: https://github.com/MontaVista-OpenSourceTechnology/meta-montavista-cgx/blob/4a74d7d1d956a3320e829eaec14e06036fa0307c/recipes-devtools/libunwind/libunwind_1.6.%25.bbappend
When this pattern is used across multiple bbappends, it triggers the following false positive: warning:oelint.var.multiinclude:'${PN}_mvista.inc' is included multiple times
This warning highlights two issues: First, it appears that this check operates at the global distro level instead of examining includes per recipe. Second, variables are not expanded, which would correctly resolve into unique include filenames.
The text was updated successfully, but these errors were encountered: