15010 2023-01-18 11:17:37 +0000 native.bbclass is unable to clear unconditional overrides during dependency rewriting 2023-03-07 12:25:08 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake unspecified All Multiple RESOLVED FIXED Medium+ normal 4.2 M4 1 ejo richard.purdie ejo poky.bs.watcher poky.watcher randy.macleod yocto --- --- Don't know oldest_to_newest 94749 0 ejo 2023-01-18 11:17:37 +0000 When using DEPENDS:append = " something" in a recipe that uses BBCLASSEXTED += "native", the generated DEPENDS list (after parsing the -native variant) will contain both "something-native" as well as "something". (The latter is then an unexpected target dependency in a -native recipe.) What should happen instead is that the override (:append) gets cleared during `map_dependencies()` of native.bbclass. Instead, it is applied twice (once during native mapping, and again at the finalization of DEPENDS). That the appends are not cleared is caused by d.setVar(varname, " ".join(newdeps), parsing=True) being called with 'parsing=True' introduced by https://git.yoctoproject.org/poky/commit/meta/classes/native.bbclass?id=c4257ed8b1040a5a0e9a95846d81961741239116. While not clearing overrides is valid for *conditional* overrides, it is not for *unconditional* ones. However, at the moment there is no bitbake API allowing us to differentiate this. One possible solution to this mentioned by RP in #yocto is implementing 'filters' as proposed by JPEW: https://git.yoctoproject.org/poky-contrib/log/?h=jpew/bb-filters 94781 1 richard.purdie 2023-01-20 12:50:12 +0000 I made some tests and it looks like for whatever reason we can now remove the parsing=True. I'll send a patch. Ultimately it would be better to switch to some filtering mechanism but that is for another day. 95071 2 richard.purdie 2023-03-07 12:25:08 +0000 https://git.yoctoproject.org/poky/commit/meta/classes-recipe/native.bbclass?id=e3ada9938ce44f7b25e3040900a553fff8540008