summaryrefslogtreecommitdiffstats
path: root/meta-selftest/conf
Commit message (Collapse)AuthorAgeFilesLines
* The poky repository master branch is no longer being updated.Richard Purdie2025-11-075-29/+0
| | | | | | | | | | | | | | | | | | | | | You can either: a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs b) use the new bitbake-setup You can find information about either approach in our documentation: https://docs.yoctoproject.org/ Note that "poky" the distro setting is still available in meta-yocto as before and we continue to use and maintain that. Long live Poky! Some further information on the background of this change can be found in: https://lists.openembedded.org/g/openembedded-architecture/message/2179 Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/bblayers.py: add tests for adding new built-in fragmentsAntonin Godard2025-10-011-0/+2
| | | | | | | | | | | | | | | | | | | | | Add discussed in [1], our best option for customizing built-in fragments is to pass them from a layer configuration. In short, the reason is that our statement must be parsed before the addfragments call is parsed.We also have to use the :append override as using += would override the original definition of OE_FRAGMENTS_BUILTIN (since it uses a ?= assignment). Provide a test case for customizing built-in fragments with meta-selftest. [1]: https://lore.kernel.org/yocto-docs/20250925-fragments-v1-0-c9f747361fb2@bootlin.com/T/#m9f7c9f110c084eba17e0f64d8b2ac7a88af3f38e Cc: Alexander Kanavin <alex.kanavin@gmail.com> (From OE-Core rev: 38cbf4c0ce5173dc3080fa0fbb3ec3e7926c8137) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update to whinlatter release seriesRichard Purdie2025-06-201-1/+1
| | | | | | | | | | Since there are currently multiple breaking changes, update to a new release series for the next release so layers can show compatibility correctly. (From OE-Core rev: 75eb26e71dba4096d5632b7f6b13db4f13aa6d7f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bbconfigbuild/configfragments.py: set BBPATH in standalone datastoreAlexander Kanavin2025-01-091-0/+2
| | | | | | | | | | | | | | | | 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>
* bitbake-config-build: add a plugin for config fragmentsAlexander Kanavin2024-12-132-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* layer.conf: Update to new layer/release series post-releaseRichard Purdie2024-10-011-1/+1
| | | | | | | | Switch from styhead to walnascar (aka walna). (From OE-Core rev: 86999b5da960cbaa75eda1a75e3c42de22786677) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Post release addition/switch to styhead corenameRichard Purdie2024-04-161-1/+1
| | | | | | (From OE-Core rev: cef91ebeb3f2b1d41336fff60555064430a80397) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update for the scarthgap release seriesRichard Purdie2024-02-091-1/+1
| | | | | | | | Prepare for the scarthgap release. (From OE-Core rev: b1835e657575c29da43a15a37c673dc37044fd85) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update to nanbield release seriesRichard Purdie2023-09-101-1/+1
| | | | | | (From OE-Core rev: f212cb12a0db9c9de5afd3cc89b1331d386e55f6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update to use mickledore as the layer series nameRichard Purdie2023-01-031-1/+1
| | | | | | | | | | | | | | OE-Core has changes which do need careful evaluation for compatibilty, such as the addpylib directive. Move the core later names to mickledore so layers can mark their compatibility as such. Also increase the version number for core. If we do make further changes that need layer changes, we'll update the version again so layers can mark compatibility within the series. (From OE-Core rev: 57239d66b933c4313cf331d35d13ec2d0661c38f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base: Switch to use addpylib directive and BB_GLOBAL_PYMODULESRichard Purdie2022-12-081-0/+2
| | | | | | | | | | | | | | | Since bitbake now supports an official method to inject python modules, switch to it. Anyone using OE_EXTRA_IMPORTS will need to adjust their code accordingly, probably switching to their own module namespace. Also switch to using BB_GLOBAL_PYMODULES to list the global modules to import. (From OE-Core rev: 1f56155e91da2030ee0a5e93037c62e1349ba89f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/multiconfig: Test that multiconfigs in separate layers worksRichard Purdie2022-06-111-0/+2
| | | | | | | | | | | | | We should test that mutliconfigs from a layer work, not just build/conf. This adds such a test. [YOCTO #13566] (From OE-Core rev: 2306261fb85d5d03145989c3af9c6897111644ae) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Post release codename changesRichard Purdie2022-04-271-1/+1
| | | | | | | | Post release add langdale to the series names. (From OE-Core rev: dc3b319a5fc47372bc111da5bc26d7dda1b17598) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update to use kirkstoneRichard Purdie2022-02-211-1/+1
| | | | | | | | | Update the layers to use the kirkstone namespace. No compatibility is made for honister due to the variable renaming. (From OE-Core rev: 4a180aa5b30cc0906072d5b1e970eea41f1ce642) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update to add post 3.3 release honister seriesRichard Purdie2021-04-181-1/+1
| | | | | | (From OE-Core rev: c0f43f19fecfd16f973c2d2f8227106c46b451bb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update for hardknott release seriesRichard Purdie2021-03-151-1/+1
| | | | | | (From OE-Core rev: d430bf39f2f2ecdf989b33f7405751844d783fc5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Move to gatesgarth namingRichard Purdie2020-05-181-1/+1
| | | | | | | | | We're still compatible with dunfell from the core perspective so that is left for compatibility (probably for the next week or two). (From OE-Core rev: 1e79324f8290b820fee034b0d4a8c353027879da) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update to LAYERSERIES_CORENAME to dunfellRichard Purdie2020-03-151-1/+1
| | | | | | | | Update the layer core name to the new release name. (From OE-Core rev: 090bb3b44ba0cc01c29942c00d43e910d1ff735e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update for zeus seriesRichard Purdie2019-10-081-1/+1
| | | | | | (From OE-Core rev: a5c9709b8da6e7ad62167b5036e7f454a62aa83e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update to warrior release name seriesRichard Purdie2019-04-021-1/+1
| | | | | | (From OE-Core rev: 13e45fffb66c7cb7ba0d07bed063c0c5ce57004b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-skeleton/meta-selftest: Update to thudRichard Purdie2018-09-251-1/+1
| | | | | | (From OE-Core rev: 4c48e59c58e62d70b900c4356953f5b66fba2353) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update LAYERSERIES rocko -> sumoRichard Purdie2018-04-061-1/+1
| | | | | | | | Also set LAYERSERIES_COMPAT for core (we're compatible with ourself). (From OE-Core rev: 4aa43cd844781a07a2dbf17f21ed35c6a0100d02) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta*: Add LAYERSERIES_COMPAT and LAYERSERIES_CORENAMES markup to layer.confRichard Purdie2017-06-121-0/+2
| | | | | | | | | | | This means mismatched layers are more clearly identified to the user in cases where compatibility has not been tested. This is perhaps not as needed for the core repository (other than CORENAMES) but lets lead by example. (From OE-Core rev: cde66d5eac8e5c2821ba225dc4be4af4e0581652) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-selftest: Add qemux86copy machineRichard Purdie2015-10-011-0/+3
| | | | | | | | | | I know Martin finds something like this useful for testing sstate signatures, this adds one to meta-selftest so we can use it from oe-selftest in the sstate tests there too. (From OE-Core rev: 7ed3364b7ca61b210fce5ed014ab700e24ee470b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-selftest: create a new test layer to be used by oe-selftest scriptCorneliu Stoicescu2013-12-031-0/+10
Everything in this layer is meant to be used by tests called by scripts/oe-selftest. These are helper recipes/appends to test various bitbake options or scripts. Currently most of these files here only have "include test_recipe.inc" which is the file tests will actually use. (From OE-Core rev: 71a5053eea2aa0055663ccb2318eda866df49bb7) Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@intel.com> Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-12-28 22:10:10 +0000