Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] pixman: ignore NEON, IWMMXT, LOONGSON_MMI variables for class-native
Date: Wed, 5 Sep 2012 16:26:22 +0800	[thread overview]
Message-ID: <50470CAE.5090406@windriver.com> (raw)
In-Reply-To: <20120905081909.GL3372@jama.jama.net>



On 09/05/2012 04:19 PM, Martin Jansa wrote:
> On Wed, Sep 05, 2012 at 02:11:41PM +0800, Robert Yang wrote:
>>
>>
>> On 09/05/2012 09:05 AM, Martin Jansa wrote:
>>> * pixman-native can have different do_configure sstate checksums if it's built with armv4t machine and armv7a
>>>     OE @ ~ $ bitbake/bin/bitbake-diffsigs
>>>       before-mgmt/stamps.1346795706/nokia900/x86_64-linux/pixman-native-*.do_configure.sigdata.*
>>>       after-mgmt/stamps.1346801508/om-gta02/x86_64-linux/pixman-native-*.do_configure.sigdata.*
>>>     basehash changed from 27e577de60880a788c7aaba797ef83e0 to c6799807eb3e767daf1e75738fc753f7
>>>     Variable NEON value changed from   to  --disable-arm-neon
>>> * so if you start building with different machine then last time (wrt
>>>     NEON setting) all recipes which depends on pixman-native will be rebuilt too
>>> * this explains why sstate-cache-management.sh wanted to remove many
>>>     native sstate packages when --stamps-dir option was used (see comment
>>>     28 in https://bugzilla.yoctoproject.org/show_bug.cgi?id=2897)
>>>
>>> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
>>> ---
>>>    meta/recipes-graphics/xorg-lib/pixman_0.27.2.bb | 5 +++--
>>>    1 file changed, 3 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/meta/recipes-graphics/xorg-lib/pixman_0.27.2.bb b/meta/recipes-graphics/xorg-lib/pixman_0.27.2.bb
>>> index 35a2def..218808a 100644
>>> --- a/meta/recipes-graphics/xorg-lib/pixman_0.27.2.bb
>>> +++ b/meta/recipes-graphics/xorg-lib/pixman_0.27.2.bb
>>> @@ -15,7 +15,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=14096c769ae0cbb5fcb94ec468be11b3 \
>>>    DEPENDS += "zlib libpng"
>>>    BBCLASSEXTEND = "native"
>>>
>>> -PR = "r1"
>>> +PR = "r2"
>>>
>>>    PE = "1"
>>>
>>> @@ -25,7 +25,8 @@ NEON = " --disable-arm-neon "
>>>    NEON_armv7a = " "
>>>    NEON_armv7a-vfp-neon = " "
>>>
>>> -EXTRA_OECONF="--disable-gtk ${IWMMXT} ${LOONGSON_MMI} ${NEON}"
>>> +EXTRA_OECONF = "--disable-gtk ${IWMMXT} ${LOONGSON_MMI} ${NEON}"
>>> +EXTRA_OECONF_class-native = "--disable-gtk"
>>>
>>
>> Hi Martin,
>>
>> What's the differences between "_virtclass-native" and "_class-native", please?
>
> _class-foo works for all types of recipes:
> target,native,cross,crosssdk,cross-canadian,nativesdk
>
> classes/base.bbclass:CLASSOVERRIDE ?= "class-target"
> classes/cross-canadian.bbclass:CLASSOVERRIDE = "class-cross-canadian"
> classes/cross.bbclass:CLASSOVERRIDE = "class-cross"
> classes/crosssdk.bbclass:CLASSOVERRIDE = "class-crosssdk"
> classes/native.bbclass:CLASSOVERRIDE = "class-native"
> classes/nativesdk.bbclass:CLASSOVERRIDE = "class-nativesdk"
> conf/bitbake.conf:OVERRIDES = "${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:build-${BUILD_OS}:pn-${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}:${CLASSOVERRIDE}:forcevariable"
> conf/bitbake.conf:CLASSOVERRIDE ?= "class-target"
>
> while _virtclass-foo works only for cross, native, nativesdk and multilib
> classes/cross.bbclass:    bb.data.setVar("OVERRIDES", e.data.getVar("OVERRIDES", False) + ":virtclass-cross", e.data)
> classes/native.bbclass:    e.data.setVar("OVERRIDES", e.data.getVar("OVERRIDES", False) + ":virtclass-native")
> classes/nativesdk.bbclass:    e.data.setVar("OVERRIDES", e.data.getVar("OVERRIDES", False) + ":virtclass-nativesdk")
> classes/populate_sdk_base.bbclass:        overrides = d.getVar("OVERRIDES", False) + ":virtclass-multilib-" + item
> classes/utils.bbclass:        overrides = localdata.getVar("OVERRIDES", False) + ":virtclass-multilib-" + item
> recipes-core/eglibc/eglibc-ld.inc:        overrides = localdata.getVar("OVERRIDES", False) + ":virtclass-multilib-" + item
>
> IIRC RP said somewhere that virtclass usages should be
> cleaned from metadata and replaced with stronger CLASSOVERRIDE, that's
> why I used class-native here.
>

Got it, thank you very much, Paul and Martin.

// Robert

> Cheers,
>



  reply	other threads:[~2012-09-05  8:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05  1:05 [PATCH 1/2] pixman: merge meta-oe append into oe-core Martin Jansa
2012-09-05  1:05 ` [PATCH 2/2] pixman: ignore NEON, IWMMXT, LOONGSON_MMI variables for class-native Martin Jansa
2012-09-05  6:11   ` Robert Yang
2012-09-05  8:01     ` Paul Eggleton
2012-09-05  8:19     ` Martin Jansa
2012-09-05  8:26       ` Robert Yang [this message]
2012-09-05 20:29         ` Richard Purdie
2012-09-10 15:42 ` [PATCH 1/2] pixman: merge meta-oe append into oe-core Saul Wold

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50470CAE.5090406@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox