summaryrefslogtreecommitdiffstats
path: root/meta/lib/bbconfigbuild
Commit message (Collapse)AuthorAgeFilesLines
* bbconfigbuild/configfragments.py: set BBPATH in standalone datastoreAlexander Kanavin2025-01-091-0/+1
| | | | | | | | | | | | | | | | Otherwise fragments with 'require' statements will not parse, as the parser will not be able to find files referred to by those statements. Add such a statement to the test fragment so that the scenario is tested. [YOCTO #15707] (From OE-Core rev: d88e63d1a7867b3a4ebfc57d472900136b5361d8) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/configfragements: enable/disable multiple fragements at onceJoshua Watt2025-01-081-14/+17
| | | | | | | | | | | Extends the 'enable-fragment' and 'disable-fragment' commands so that they accept multiple fragments at once as a convenience for the user (From OE-Core rev: 50c3cdb3a3b9c7daa55ff26d302d95e5f350e4d2) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/configfragments: Restrict fragment file checkingJoshua Watt2025-01-081-0/+2
| | | | | | | | | | | | | | | | | The current implementation of the config fragments is too aggressive in checking files; any file in the fragment directory is checked, including hidden files or files with weird extensions. In particular, if an editor is creating temporary backup files when editing, these will be checked and will almost assuredly fail, which prevents the tool from running. Add a filter so that only non-hidden files that end with .conf are checked. (From OE-Core rev: 93edab0e2bccacb808421f0766d587c576c1a12b) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake-config-build: add a plugin for config fragmentsAlexander Kanavin2024-12-131-0/+159
This allows fine-tuning local configurations with pre-frabricated configuration snippets in a structured, controlled way. It's also an important building block for bitbake-setup. The tool requires that each fragment contains a one-line summary, and one or more lines of description, as BB_CONF_FRAGMENT_SUMMARY style metadata. There are three (and a half) operations (list/enable/disable/disable all), and here's the 'list' output: alex@Zen2:/srv/storage/alex/yocto/build-64$ bitbake-config-build list-fragments NOTE: Starting bitbake server... Available fragments in selftest layer located in /srv/work/alex/poky/meta-selftest: Enabled fragments: selftest/test-fragment This is a configuration fragment intended for testing in oe-selftest context Unused fragments: selftest/more-fragments-here/test-another-fragment This is a second configuration fragment intended for testing in oe-selftest context (From OE-Core rev: fdb611e13bd7aa00360d3a68e4818ef5f05c8944) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>