Skip to contentSkip to conversation

how to apply bbappend selectively

DISCUSSION Jaap de Jong 2 participants 3 messages Jul 28, 2011 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

Hi All,

I.m creating a special image with for instance a modified udev package.
I've created a udev-xxx.bbappend for that purpose.
But for all the other images I build for other hardware I still want to use the original udev-xxx. There is probably a simple solution but I don't see it...
Any ideas?

Thanks in advance!
Jaap

#1 lore raw
Quoted 4 lines · On Thursday 28 July 2011 10:56:28 Jaap de Jong wrote:

I.m creating a special image with for instance a modified udev package. I've created a udev-xxx.bbappend for that purpose.
But for all the other images I build for other hardware I still want to use the original udev-xxx.

Usually this is just done with machine overrides within the bbappend.

e.g.

SRC_URI_append_somemachine = "file://somefile.patch" SOMEVARIABLE_somemachine = "value1" ANOTHERVARIABLE_somemachine = "value2"

That way building for all other machines will be unaffected.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#3 lore raw
In reply to a message not in the archive
Quoted 4 lines · On Thursday 28 July 2011 12:13:23 Jaap de Jong wrote:

But it will still create processor-related packages instead of machine-related.
I probably need some magic flag set to get it machine-related (or perhaps better: image-related)?

Well, PACKAGE_ARCH_somemachine = "${MACHINE_ARCH}" will do that; although if you're manipulating SRC_URI then it's supposed to set that automatically.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre