gnome.bbclass

gnome.bbclass

[Andreas Müller]

Hi,

we have gnome.bbclass in oe-core and meta-oe. The only difference I
see is meta-oe extends

BBCLASSEXTEND += "native"

Could somebody help me why we need to build all gnome recipes native?

Andreas

Re: gnome.bbclass

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]

On Thu, Aug 23, 2012 at 11:22:03AM +0200, Andreas Müller wrote:
> Hi,
> 
> we have gnome.bbclass in oe-core and meta-oe. The only difference I
> see is meta-oe extends
> 
> BBCLASSEXTEND += "native"
> 
> Could somebody help me why we need to build all gnome recipes native?

git log says it was because of 'hicolor-icon-theme-native' and 'gnome-common-native'

If it's not needed anymore, then it would be nice to drop meta-oe gnome.bbclass now.

Cheers,

commit aac01cbce74cef20283752c16d70043ca6d2e483
Author: Koen Kooi <koen@dominion.thruhere.net>
Date:   Sat Dec 4 18:17:26 2010 +0100

    meta-openembedded: add BBCLASSEXTEND = native to gnome.bbclass

    This fixes the missing 'hicolor-icon-theme-native' and 'gnome-common-native' deps

    Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>

diff --git a/classes/gnome.bbclass b/classes/gnome.bbclass
index 7bc5d9c..0a32a77 100644
--- a/classes/gnome.bbclass
+++ b/classes/gnome.bbclass
@@ -1,4 +1,4 @@
 inherit gnomebase gtk-icon-cache gconf mime

 EXTRA_OECONF += "--enable-introspection=no"
-
+BBCLASSEXTEND += "native"

> 
> Andreas
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: gnome.bbclass

[Burton, Ross]

On 23 August 2012 10:35, Martin Jansa <martin.jansa@gmail.com> wrote:
> git log says it was because of 'hicolor-icon-theme-native' and 'gnome-common-native'

Isn't that quite a sledgehammer approach, why couldn't BBCLASSEXTEND
+= "native" be added to just those two recipes?

Ross

Re: gnome.bbclass

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 23-08-12 23:32, Burton, Ross schreef:
> On 23 August 2012 10:35, Martin Jansa <martin.jansa@gmail.com> wrote:
>> git log says it was because of 'hicolor-icon-theme-native' and
>> 'gnome-common-native'
> 
> Isn't that quite a sledgehammer approach, why couldn't BBCLASSEXTEND +=
> "native" be added to just those two recipes?

With the current tiny set of gnome recipes, only those 2 needed it. In
OE-classic with a lot more gnome a lot more was needed. Over time the gnome
cleaned up their act as well.

KDE on the other hand....

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFQNzzsMkyGM64RGpERArH0AJ4jfChjl+AYJtk+F3dkzIp7yhY9RgCeIWN0
xtyRNgSW6v8z0jkm43GKbYA=
=ozoX
-----END PGP SIGNATURE-----

Re: gnome.bbclass

[Samuel Stirtzel]

2012/8/24 Koen Kooi <koen@dominion.thruhere.net>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Op 23-08-12 23:32, Burton, Ross schreef:
>> On 23 August 2012 10:35, Martin Jansa <martin.jansa@gmail.com> wrote:
>>> git log says it was because of 'hicolor-icon-theme-native' and
>>> 'gnome-common-native'
>>
>> Isn't that quite a sledgehammer approach, why couldn't BBCLASSEXTEND +=
>> "native" be added to just those two recipes?
>
> With the current tiny set of gnome recipes, only those 2 needed it. In
> OE-classic with a lot more gnome a lot more was needed. Over time the gnome
> cleaned up their act as well.
>
> KDE on the other hand....

I Don't know what you intend to say, but KDE is a BBOM with lots of
magical glue code ;)
My workarounds increase the "zero support for cross compiling" to
"somewhat more than zero support" that is all.

-- 
Regards
Samuel