From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: gobject introspection to oe-core
Date: Tue, 9 Feb 2016 12:37:08 +0200 [thread overview]
Message-ID: <56B9C154.2030002@linux.intel.com> (raw)
In-Reply-To: <DUB130-W6784E5708A3084D22AA513DAD60@phx.gbl>
On 02/09/2016 12:30 PM, Chris Trobridge wrote:
> One thing I failed to mention when I reported on this previously is that
> I needed to patch polkit_0.113.bb:
>
> -DEPENDS = "expat glib-2.0 intltool-native gobject-introspection-stub mozjs"
> +DEPENDS = "expat glib-2.0 intltool-native gobject-introspection mozjs"
>
> This seems quite obvious, so I am sure you're aware of it. That was all
> I needed but there are other references to gobject-introspection-stub in:
>
> meta-gnome/recipes-gnome/libwnck/libwnck_2.31.0.bb
> meta-multimedia/recipes-connectivity/gupnp/gupnp-igd_0.2.2.bb
> meta-oe/recipes-devtools/libgee/libgee_0.16.1.bb
> meta-oe/recipes-gnome/gtkextra/gtkextra_3.0.5.bb
> meta-oe/recipes-support/upower/upower_0.9.14.bb
Those recipes are all in meta-oe - fixing them is not in scope at the
moment. For now the introspection patchset is strictly for oe-core.
You are welcome to develop and maintain a companion meta-oe patchset though.
Alex
next prev parent reply other threads:[~2016-02-09 10:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 9:16 gobject introspection to oe-core Chris Trobridge
2015-12-17 9:25 ` Burton, Ross
2016-02-09 10:30 ` Chris Trobridge
2016-02-09 10:37 ` Alexander Kanavin [this message]
2016-02-23 14:51 ` alexander.kanavin
2016-01-04 11:50 ` gobject introspection - distccd? Chris Trobridge
2016-01-04 12:03 ` Burton, Ross
2016-01-04 12:24 ` Chris Trobridge
2016-01-04 12:49 ` Alexander Kanavin
2016-01-05 7:56 ` Chris Trobridge
2016-02-09 10:52 ` gobject introspection to oe-core Carlos Rafael Giani
2016-02-09 11:08 ` Alexander Kanavin
-- strict thread matches above, loose matches on Subject: below --
2015-10-06 12:27 Alexander Kanavin
2015-10-07 9:58 ` Changhyeok Bae
2015-10-08 6:29 ` Andreas Müller
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=56B9C154.2030002@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--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