> -----Original Message----- > From: Richard Purdie <[email protected]> > Sent: den 16 mars 2026 12:29 > To: Peter Kjellerstedt <[email protected]>; > [email protected] > Subject: Re: [OE-core] [PATCH] sstate/sstatesig: Abstract dummy package > architectures into layer.conf settings > > On Mon, 2026-03-16 at 11:21 +0000, Peter Kjellerstedt wrote: > > > -----Original Message----- > > > From: [email protected] > > > <[email protected] On Behalf Of Richard Purdie via > > > lists.openembedded.org > > > Sent: den 14 mars 2026 11:27 > > > To: [email protected] > > > Subject: [OE-core] [PATCH] sstate/sstatesig: Abstract dummy package > > > architectures into layer.conf settings > > > > > > Other layers need to be able to add dummy recipes. To do this add > > > DUMMY_PACKAGE_ARCHS_SDK and DUMMY_PACKAGE_ARCHS_TARGET in layer.conf > > > which can be used to add these to the right places in the code. > > > > > > Don't add the variables to task signatures as these only matter in the > > > context of constructed images and not the recipes. > > > > > > d-off-by: Richard Purdie <[email protected]> > > > --- > > > meta/classes-global/sstate.bbclass | 7 +++---- > > > meta/conf/layer.conf | 3 +++ > > > meta/lib/oe/sstatesig.py | 9 +++------ > > > 3 files changed, 9 insertions(+), 10 deletions(-) > > > > > > diff --git a/meta/classes-global/sstate.bbclass > > > b/meta/classes-global/sstate.bbclass > > > index a7c3f5332a2..fe70a976869 100644 > > > --- a/meta/classes-global/sstate.bbclass > > > +++ b/meta/classes-global/sstate.bbclass > > > @@ -86,14 +86,13 @@ SSTATE_ARCHS = " \ > > > ${BUILD_ARCH}_${ORIGNATIVELSBSTRING} \ > > > ${BUILD_ARCH}_${SDK_ARCH}_${SDK_OS} \ > > > ${SDK_ARCH}-${SDKPKGSUFFIX} \ > > > - buildtools-dummy-${SDKPKGSUFFIX} \ > > > - sdk-provides-dummy-target \ > > > - sdk-provides-dummy-${SDKPKGSUFFIX} \ > > > + ${DUMMY_PACKAGE_ARCHS_SDK} \ > > > + ${DUMMY_PACKAGE_ARCHS_TARGET} \ > > > allarch \ > > > ${SSTATE_ARCHS_TUNEPKG} \ > > > ${PACKAGE_EXTRA_ARCHS} \ > > > ${MACHINE_ARCH}" > > > -SSTATE_ARCHS[vardepsexclude] = "ORIGNATIVELSBSTRING" > > > +SSTATE_ARCHS[vardepsexclude] = "ORIGNATIVELSBSTRING > > > DUMMY_PACKAGE_ARCHS_SDK DUMMY_PACKAGE_ARCHS_TARGET" > > > > > > SSTATECREATEFUNCS += "sstate_hardcode_path" > > > SSTATECREATEFUNCS[vardeps] = "SSTATE_SCAN_FILES" > > > diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf > > > index ba25ca30296..4794e660aed 100644 > > > --- a/meta/conf/layer.conf > > > +++ b/meta/conf/layer.conf > > > @@ -133,6 +133,9 @@ SSTATE_EXCLUDEDEPS_SYSROOT += "\ > > > # dependency in the recipe. > > > SSTATE_EXCLUDEDEPS_SYSROOT += ".*->autoconf-archive-native" > > > > > > +DUMMY_PACKAGE_ARCHS_SDK = "buildtools-dummy-${SDKPKGSUFFIX} > > > sdk-provides-dummy-${SDKPKGSUFFIX}" > > > +DUMMY_PACKAGE_ARCHS_TARGET = "sdk-provides-dummy-target" > > > > Wouldn't it be more appropriate to use += for these two? > > Otherwise one will have to use :append to add to them in other > > layers. > > That depends on whether your layer is included after core or not. I'd > have thought including before core would be potentially problematic > anyway...
Sure, but with += the order does not matter. > > Cheers, > > Richard We have "meta" as the last layer in BBLAYERS in our setup. E.g., these are the external layers I have in one of our configurations: BBLAYERS ?= " \ ... .../meta-virtualization \ .../meta-webserver \ .../meta-multimedia \ .../meta-filesystems \ .../meta-networking \ .../meta-python \ .../meta-oe \ .../meta-poky \ .../meta \ " We have them configured like this to as best as possible match the layer priorities. It is not perfect (e.g., meta-poky prepends to BBPATH instead of appending like all the other layers do), but it has resulted in the least surprises regarding things that are based on BBPATH and things that are based on layer priorities. //Peter
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#233251): https://lists.openembedded.org/g/openembedded-core/message/233251 Mute This Topic: https://lists.openembedded.org/mt/118311664/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
