From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gobject-introspection: Drop the recipe, it has never worked and if it does cross compile, we can add it back
Date: Fri, 27 Jul 2012 13:18:57 +0100 [thread overview]
Message-ID: <1343391537.9574.132.camel@ted> (raw)
In-Reply-To: <20120727114631.GJ3621@jama.jama.net>
On Fri, 2012-07-27 at 13:46 +0200, Martin Jansa wrote:
> On Fri, Jul 27, 2012 at 12:43:14PM +0100, Richard Purdie wrote:
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > ---
> > diff --git a/meta/recipes-gnome/gnome/gobject-introspection_1.32.1.bb b/meta/recipes-gnome/gnome/gobject-introspection_1.32.1.bb
> > deleted file mode 100644
> > index 8f5ca56..0000000
> > --- a/meta/recipes-gnome/gnome/gobject-introspection_1.32.1.bb
> > +++ b/dev/null
> > @@ -1,28 +0,0 @@
> > -# NOTE: WIP! This recipe does not cross-compile atm., only -native
> > -DEPENDS = "glib-2.0 libffi python-native gobject-introspection-native"
> > -DEPENDS_virtclass-native = "glib-2.0-native libffi-native python-native bison-native flex-native"
> > -BBCLASSEXTEND = "native"
>
>
> what will provide gobject-introspection-native for meta-oe and meta-gnome now?
>
> Or should we add this recipe back in meta-oe?
Is introspection being used there of do they just want the .m4 file and
disable it?
If the latter, add "gobject-introspection-stub" to DEPENDS and this
should resolve it. See the patches I just sent doing this for OE-Core.
Cheers,
Richard
next prev parent reply other threads:[~2012-07-27 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 11:43 [PATCH] gobject-introspection: Drop the recipe, it has never worked and if it does cross compile, we can add it back Richard Purdie
2012-07-27 11:46 ` Martin Jansa
2012-07-27 11:48 ` Burton, Ross
2012-07-27 12:18 ` Richard Purdie [this message]
2012-07-27 13:49 ` Colin Walters
2012-07-27 14:10 ` Richard Purdie
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=1343391537.9574.132.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
/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