From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
tomas@sleepfive.com, changhyeok.bae@gmail.com
Subject: gobject introspection to oe-core
Date: Tue, 06 Oct 2015 15:27:14 +0300 [thread overview]
Message-ID: <5613BE22.7020801@linux.intel.com> (raw)
Hello,
I'm looking into the possibility of adding gobject introspection support
directly to oe-core for Yocto 2.1 release (Spring 2016). This work would
of course be based on meta-gir, but with the mandatory goal of producing
patches of sufficient quality that can be sent upstream.
I know the upstream tarball is a mess that mashes together several
different things and was never designed for cross-compiling; and
meta-gir is also difficult to understand: autotools-based build files
are patched using undocumented patchfiles, then again patched from the
recipe using sed, with no comments anywhere - all that needs to be sorted.
What's your take on this? Is it realistic? Would you be able to help out?
Regards,
Alexander
next reply other threads:[~2015-10-06 12:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 12:27 Alexander Kanavin [this message]
2015-10-07 9:58 ` gobject introspection to oe-core Changhyeok Bae
2015-10-08 6:29 ` Andreas Müller
-- strict thread matches above, loose matches on Subject: below --
2015-12-17 9:16 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-02-09 10:52 ` 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=5613BE22.7020801@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=changhyeok.bae@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=tomas@sleepfive.com \
/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