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>
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>
Switch from styhead to walnascar (aka walna).
(From OE-Core rev: 86999b5da960cbaa75eda1a75e3c42de22786677)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Prepare for the scarthgap release.
(From OE-Core rev: b1835e657575c29da43a15a37c673dc37044fd85)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
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>
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>
Post release add langdale to the series names.
(From OE-Core rev: dc3b319a5fc47372bc111da5bc26d7dda1b17598)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
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>
Update the layer core name to the new release name.
(From OE-Core rev: 090bb3b44ba0cc01c29942c00d43e910d1ff735e)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
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>
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>
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>
