From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: gobject introspection - distccd?
Date: Mon, 4 Jan 2016 14:49:13 +0200 [thread overview]
Message-ID: <568A6A49.7030508@linux.intel.com> (raw)
In-Reply-To: <DUB130-W21AF20AA18BC334FB9E61BDAF20@phx.gbl>
On 01/04/2016 02:24 PM, Chris Trobridge wrote:
> That's what I was thinking: gobject-introspection doesn't call it in
> directly but it does require compilation to be performed on the 'target'
> system and that could pull it in indirectly.
g-introspection does not require compilation to be performed on the
target. It requires running binaries that were cross-compiled for the
target architecture, which is achieved by running them using qemu.
> distcc (and hence avahi) are not required, so is this a general problem
> or just something I should explicitly remove from my image?
I think it's a problem of your local setup; the g-o patchset definitely
doesn't involve distcc at any point. You can build against a clean
directory with only basic poky layers to verify that.
Alex
next prev parent reply other threads:[~2016-01-04 12:52 UTC|newest]
Thread overview: 12+ 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
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 [this message]
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
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=568A6A49.7030508@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