13206 2019-02-26 21:38:07 +0000 Bitbake needs a lint-like tool 2026-08-13 15:28:08 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake unspecified x86 Multiple NEW Medium enhancement 6.99 1 evadeflow unassigned duy.dang.yw pavel poky.bs.watcher poky.watcher randy.macleod --- --- Don't know oldest_to_newest 83128 0 evadeflow 2019-02-26 21:38:07 +0000 I feel it would benefit the Yocto project *tremendously* to have a linter for Bitbake builds. Bitbake is quite liberal in terms of what it will permit recipe/layer authors to do. However, a set of best practices have emerged over the past several years, many of which take the form: "Avoid X." Here are a few such rules I encountered this week: - In general, avoid override-style removal (i.e., `FOO_remove = ...`), because it's extremely difficult to undo in append recipes. If you must use this syntax, prefer the idiom`FOO_remove = ${FOO_REMOVALS}` so that appends can override the removal. - Avoid adding extra whitespace when using += and =+ BAD: FOO += " bar" OKAY: FOO += "bar" - Avoid forgetting to add whitespace when appending via override syntax. BAD: FOO_append = "bar" OKAY: FOO_append = " bar" My guess is that core Yocto project contributors can rattle off a few dozen rules like this off the top of their head. And I'm betting that automated checks could be written for many/most of them. 96824 1 randy.macleod 2023-10-24 14:24:25 +0000 Bulk move from 4.99 or 0.00 to 5.99 98513 2 duy.dang.yw 2024-03-18 03:48:13 +0000 There is a python library for this purpose: https://pypi.org/project/oelint-adv/ But can we use it in bitbake or create a contrib script in poky?