[oe] Common patch directory for a set of boards.

Ulf Samuelsson ulf.samuelsson at atmel.com
Thu Aug 13 20:49:10 UTC 2009


Is there a way to store a patch which is applied to a list of boards,
but not every board, in a common directory?

SRC_URI_append_at91sam9263ek += "file://atmel.patch;patch=1"
SRC_URI_append_at32stk1000 += "file://atmel.patch;patch=1"
SRC_URI_append_at572d940hf += "file://atmel.patch;patch=1"
SRC_URI_append_beta1 += "file://beta.patch;patch=1"
SRC_URI_append_beta2 += "file://beta.patch;patch=1"
SRC_URI_append_beta3 += "file://beta.patch;patch=1"
SRC_URI_append_caesar1 += "file://caesar.patch;patch=1"
SRC_URI_append_caesar2 += "file://caesar.patch;patch=1"

with a file system like:

<recipe>
	recipe-1.0/atmel/atmel.patch
	recipe-1.0/beta/beta.patch
	recipe-1.0/caesar/caesar.patch
	recipe-1.0.bb


instead of

<recipe>
	recipe-1.0/at91sam9263ek/atmel.patch
	recipe-1.0/at32stk1000/atmel.patch
	recipe-1.0/at572d940hf/atmel.patch
	recipe-1.0/beta1/beta.patch
	recipe-1.0/beta2/beta.patch
	recipe-1.0/beta3/beta.patch
	recipe-1.0/caesar1/caesar.patch
	recipe-1.0/caesar2/caesar.patch
	recipe-1.0.bb


I can think of symlinking at91sam9263ek to at572d940hf
but then you cannot have a defconfig file per board.

Maybe you can specify:

SRC_URI_append_at91sam9263ek += "file://../atmel/atmel.patch;patch=1"

but this has a fould look about it.

FOr the at91 patches, I took the easy way out and put all the patches
on www.at91.com, which is no good, since it has been down for
almost two days :-(



-- 
Best Regards
Ulf Samuelsson





More information about the Openembedded-devel mailing list