From: Colin Helliwell <colin.helliwell@ln-systems.com>
To: yocto@yoctoproject.org
Subject: Re: gobject introspection needing pygobject (cross-compilation)
Date: Fri, 31 Mar 2017 08:36:56 +0100 (BST) [thread overview]
Message-ID: <77506290.327975.1490945816640@email.1and1.co.uk> (raw)
In-Reply-To: <6783352e-1f5e-e1fe-9979-96b5cb4f82d9@linux.intel.com>
> On 31 March 2017 at 08:26 Alexander Kanavin <alexander.kanavin@linux.intel.com> wrote:
>
> On 03/31/2017 09:06 AM, colin.helliwell@ln-systems.com wrote:
>
> > I've got a few packages in my image which need gobject introspection.
> > (x86-64 host, ARM target)
> > One is building fine, but the other - NetworkManager - is failing to
> > generate the introspection data because it can't analyse the cross-compiled
> > library. Apparently it uses pygobject in doing this, and thus needs a
> > version of that for the target architecture.
> > Are there steps I can take to achieve this? I guess it needs some 'qemu'
> > technique as with other the G-I support mechanisms?
>
> I guess you have read and understood the section in the Yocto manual
> dedicated to this?
>
Project Dev Manual 5.7? Yep, have read that. In fact, I've been able to enable g-i on ModemManager, and on NetworkManager 1.4 - but there's something new about 1.6/1.8 that's throwing this problem.
> To provide useful help, I need to see specifics. What is the error
> message you are getting? Where are your recipes, and which one is failing?
>
Sure. I'll put together additional info.
next prev parent reply other threads:[~2017-03-31 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 6:06 gobject introspection needing pygobject (cross-compilation) colin.helliwell
2017-03-31 7:26 ` Alexander Kanavin
2017-03-31 7:36 ` Colin Helliwell [this message]
2017-03-31 7:31 ` Jussi Kukkonen
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=77506290.327975.1490945816640@email.1and1.co.uk \
--to=colin.helliwell@ln-systems.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.