01:10 <ndeuteron> Hello #yocto. In the past I've used langdale to build SDKs targeting arm64 and amd64 so that I can build stuff for an imx8 as well as for PCs using essentially the same build environment and instructions. Now, with scarthgap, I'm having trouble with all the required meta layers for both machines coexisting. Is this considered a bug? Or is it expected now that I should have separate kas configs for

01:10 <ndeuteron> building each SDK?

09:14 <RP> ndeuteron: what kind of trouble? Hard to say without knowing the details but I'd have thought it should work

10:17 <ndeuteron> RP: I've got it working with BBMASK:genericx86-64 now, to mask off some bits that were causing problems.

10:18 <ndeuteron> Some of it is some inhouse stuff from another team, but meta-imx was causing me some grief too, I thought.

10:18 <ndeuteron> I'll try enabling that layer again in a bit and see what falls over.

10:25 <RP> ndeuteron: the imx stuff is known to be problematic, we don't control that :(

10:26 <ndeuteron> Ah, right. This comes from NXP, doesn't it?

10:27 <ndeuteron> I guess my BBMASK is probably the way to go then. It's only 3 lines. Not too bad.

10:44 <RP> ndeuteron: it does, yes

11:23 <rburton> RP JPEW: proposal: start migrating pkgdata from the ugly existing files to just being in the json. the existing format is a pita to parse.

11:38 <RP> rburton: seems reasonable to me. They predate json support in python

11:59 <kanavin> ndeuteron, you can create two different templates with separate bblayers.conf.sample files?

11:59 <kanavin> then initialize builds pointing to one or the other

12:00 <kanavin> in theory layers shouldn't overstep, but we can't control vendors, and they sometimes butcher yocto

13:46 <JPEW> rburton: agreed

14:01 <rburton> JPEW: fyi https://github.com/popey/sbommage/issues/5

14:02 <JPEW> Cool