[OE-core] gobject introspection to oe-core

[Carlos Rafael Giani]

This is very interesting. Once gobject introspection is in place, vala 
based software like Rygel can finally be compiled directly from the vala 
source, which makes it much easier to apply patches against it.
Also, I think the GStreamer 1.0 Python bindings need GIR. This recipe 
could then be reintroduced (it was there, but got removed).

On 2015-12-17 10:16, Chris Trobridge wrote:
> Hi,
>
> I have done some testing of Alex's branch 
> "akanavin/gobject-introspection-experimental", originally 
> http://patchwork.openembedded.org/patch/107089/ 
> <http://patchwork.openembedded.org/patch/107089/%0A><http://patchwork.openembedded.org/patch/107089/%0A>
>
> I have built this successfully for x86 and x64 targets on an x64 build 
> machine:
>
> meta
> meta-yocto
> meta-yocto-bsp    = 
> "akanavin/gobject-introspection-experimental:04c7746ce90abc14604dec3328b9472c53cccf98"
> meta-networking
> meta-oe
> meta-python       = "master:47f7d287a09329734629cb9d194ef4e077117d79"
> meta-haswell-wc
> meta-intel        = "master:6e91701dcf68f9351db8bb0b92eb2d26af1b8f7f"
> meta-systemd      = "master:47f7d287a09329734629cb9d194ef4e077117d79"
>
> Specifically, it built for the qemux86, qemux86-64 and hasell-wc machines.
>
> I have successfully run my own python3 service, which uses python3 
> dbus and GObject from gi.repository.
>
> I have also inherited gobject-introspection into modemmanager_1.4.2.bb 
> from meta-oe, which fixed the recipe building and I have checked that 
> the target executable runs but not tested its dbus interface yet.
>
> Regards,
> Chris
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160209/7cfcced9/attachment-0002.html>