[OE-core] [PATCH] mesa-dri: move extra DRIMODULES to EXTRA_DRIMODULES

Martin Jansa martin.jansa at gmail.com
Fri Oct 21 07:34:19 UTC 2011


On Sat, Oct 15, 2011 at 7:02 PM, Richard Purdie
<richard.purdie at linuxfoundation.org> wrote:
> On Sat, 2011-10-15 at 12:38 +0200, Martin Jansa wrote:
>> * this way we can use
>>   EXTRA_DRIDRIVERS_armv4t += ",glamo" in meta-openmoko layer and
>>   EXTRA_DRIDRIVERS_armv4t += ",foo" in meta-bar layer without knowledge
>>   of other modules in other layers in stack
>> * actually it's like old MACHINE_DRI_MODULES from OE-classic but renamed
>>   to indicate that it should be used for architecture not machine
>
> This is way overcomplicated. Just do:
>
> DRIDRIVERS_append_armv4t = ",glamo"

Ah, is it expected that armv4t is no longer valid OVERRIDE?

OVERRIDES="linux-gnueabi:arm:build-linux:pn-libdrm:om-gta02::shr:forcevariable:thumb:libc-glibc"

# OVERRIDES=${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:build-${BUILD_OS}:pn-${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}:forcevariable${@bb.utils.contains("TUNE_FEATURES",
"thumb", ":thumb", "", d)}${@bb.utils.contains("TUNE_FEATURES",
"no-thumb-interwork", ":thumb-interwork", "", d)}:libc-glibc

So I've to change it to
DRIDRIVERS_append_arm
or is it TRANSLATED_TARGET_ARCH fault?

Regards,




More information about the Openembedded-core mailing list