linux/poky.git/bitbake/lib, branch 5.2_M1

bitbake: lib/bb/tests: use bb.build.listtasks() instead of __BBTASKS

2024-12-13T10:44:35+00:00

Use the new listtasks() function (introduced in 185c4b) to avoid accessing a private variable. Also use assertSequenceEqual() directly as we don't really care about the actual type returned, only that it's a sequence. (Bitbake rev: 452289efc6d3608ceca321286fd5bf417a6e1bed) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bitbake: bitbake: parse: add support for flagged fragment variables

2024-12-13T10:44:35+00:00

It was suggested that using flags in fragment content to mark fragment-specific metadata (such as descriptions and dependencies) is prone to quiet regressions when fragments are renamed or moved, and it clutters the fragment content. With this change allowed fragment metadata variables must be explicitly listed in a variable that is given to addfragment directive, and parser will add the flag containing the fragment name to them. (Bitbake rev: ed9a3ca9426500511feb77f41a146953dbfe9af7) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

bitbake: parse: add support for 'addfragments' directive

2024-12-08T22:36:11+00:00

It takes two parameters: - location prefix for fragments - name of variable that holds the list of enabled fragments, each of them prefixed by layer id Implementation of this directive essentially expands the fragment list obtained from the variable into absolute fragment paths and hands them to the implementation of 'require'. (Bitbake rev: f687746703e7b096c5480668fd4f49bd4951182b) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

bitbake: parse/ConfHandler: allow / in variable flags

2024-12-08T22:36:11+00:00

This is beneficial for config fragments, as their names are specified via flags, and those names can include slashes: BB_CONF_FRAGMENT_SUMMARY[init/systemd] = "This fragment enables systemd as an init manager" (Bitbake rev: 80805988492b35593067230f68782a5687c8f557) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

bitbake: cooker: use enum for cooker state to improve readability

2024-12-06T23:33:54+00:00

enum was introduced in Python 3.4 (Bitbake rev: 35b71a94f8757fcca830f972a42edab1dd000c16) Signed-off-by: Chris Laplante Signed-off-by: Richard Purdie

bitbake: server/xmlrpcserver: fix some warnings

2024-12-06T23:33:54+00:00

+ Unnecessary parens + Missing imports + Instance attribute defined outside of __init__ (Bitbake rev: 0622b3df9a55ed66009f3bed47fbf52bb2122056) Signed-off-by: Chris Laplante Signed-off-by: Richard Purdie

bitbake: knotty: some small cleanups while I'm in here

2024-12-06T23:33:54+00:00

+ missing imports + indentation fix + missing call to super __init__ + redundant parenthesis (Bitbake rev: 89613f4ba31377528d1934cc591fe33218bd916a) Signed-off-by: Chris Laplante Signed-off-by: Richard Purdie

bitbake: knotty: print an error if MACHINE is not set

2024-12-06T23:33:54+00:00

When the user forgets to set MACHINE, bitbake just exits without printing anything. This is because BB_CONSOLELOG ends up with an unexpanded '${MACHINE}', which bb.utils.mkdirhier tries to report using bb.fatal. But bb.fatal utilizes the very logging infrastructure that this code was trying to setup. (Bitbake rev: 7d3f3655b2f610f76898c84b8b97ef2e26529c41) Signed-off-by: Chris Laplante Signed-off-by: Richard Purdie

bitbake: runqueue: Fix scenetask processing performance issue

2024-11-29T22:13:25+00:00

Analysis shows that "bitbake core-image-ptest-all" spends a lot of time in scenequeue_updatecounters and much of it is rebuilding a set which doens't change. Reorder the code to avoid that performance glitch. (Bitbake rev: 923c19b9713e398d8e66e6d4422dfd4c18a03486) Signed-off-by: Richard Purdie

bitbake: runqueue: Optimise setscene loop processing

2024-11-29T22:13:25+00:00

Rather than looping through things we looped through on the previous execution, start looping where we left off for setscene processing. This gives speed improvements depending on the kind of build being executed. (Bitbake rev: 00f4d932e3af0eeb333339cbe942010fc76dee0f) Signed-off-by: Richard Purdie