Closed adrians closed 3 years ago
Thanks a lot for this details description, even more given the size of your change! Usually, it's just the other way around: tones of changes and very few words on the reasoning.
I've two wishes, this:
Okay, I've solved the two items.
Merged into next.
In order for oe-core to correctly display the layers and revisions used in a build, the paths used in conf/bblayers.conf must have no trailing path separator.
More precisely, oe-core uses the following code to display the list of layers, branches and commits used:
It expects no trailing slash at the end of the layer's path (as read from
conf/bblayers.conf
), as having a trailing slash makes theos.path.basename
returns the empty string.Proof:
In my case, using kas 2.2, while using the following yaml config, it was generating a
conf/bblayers.conf
file containing trailing slashes:YAML:
bblayers.conf:
When attempting to use bitbake, the meta-raspberrypi layer name is not displayed in the logs, but its hash appears.
After applying the attached fix, the
conf/bblayers.conf
is generated without any trailing slash in the layer's path:Also, bitbake renders the list of layers correctly