#yocto #yocto
Monsees, Steven C (US)
I am currently looking at porting from “rocko” to “zeus”…
Under your migration pages, I saw that in the project 2.7 release the following change occurred to BitBake:
“Bitbake now checks BBFILE_COLLECTIONS for duplicate entries and triggers an error if any are found.”
Does this imply that Yocto/BitBake would now throw a “duplicate BBFILE_COLLECTIONS”, if say prior to 2.7 one had 2 layers such as:
(1) ./workspace_1/poky/../meta-intel (2) ./workspace_1/poky/../meta-1/meta-2/meta-intel
Where #1 was the actual meta-intel recipe, and #2 was for modification/configuration of #1 ?
Thanks, Steve
|
|
Monsees, Steven C (US)
Maybe the better question is, Does the BBFILE_COLLECTIONS name add now have to be unique ? In this scenario the BBFILE_COLLECTIONS name is currently set to += "intel" for both the respective layer.conf files... Currently under the "rocko" release this does not cause an isuue. Thanks, Steve
|
|
mail@...
Hey, Yes it got changed to make it clear that it has to be unique. You will get slot of fun when updating to dunfell. Also each recipes will have its own sysroot. Cheers
On Oct 29, 2020 20:37, "Monsees, Steven C (US) via lists.yoctoproject.org" <steven.monsees=baesystems.com@...> wrote:
|
|
Monsees, Steven C (US)
I am not sure I am following ... #1 is the actual package being built, #2 is the mods to the recipes for the image I am building... (1) ./workspace_1/poky/../meta-intel (2) ./workspace_1/poky/../meta-1/meta-2/meta-intel
|
|
Martin Jansa
your 2nd meta-intel probably still has: LICENSE_PATH += "${LAYERDIR}/custom-licenses" in layer.conf without having this directory included in the layer?
On Mon, Nov 2, 2020 at 1:37 PM Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@...> wrote:
|
|
Monsees, Steven C (US)
Thanks you, that was the issue...
|
|