All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 1/2] package/gobject-introspection: add package
Date: Fri, 18 Aug 2017 00:39:06 +0200	[thread overview]
Message-ID: <346fcaef-6d03-4d57-c749-da966016d401@mind.be> (raw)
In-Reply-To: <1502952247260-173614.post@n4.nabble.com>



On 17-08-17 08:44, Alexey Roslyakov wrote:
> Hi Adam,
> 
> I experience the same difficulties because of lack of object-introspection.

 I agree that gobject-introspection would definitely be nice to have, but it is
complicated... And somebody will have to do the work!

 In addition to the comments made on Sam's patch, here are some additional
sources of information.

[1] describes a Linaro study of the possibilities of cross-compiling
gobject-introspection. It's kind of wordy, but the bottom line is: almost
impossible. It dates from 2011 but I don't think things have changed fundamentally.

[2] shows the gobject-introspection architecture, which explains the different
steps and how they fit together. Something like this should definitely be part
of the commit message. From this, I gather that g-ir-compiler is the problem,
because it's not g-ir-cross-compiler :-)

[3] describes how it is solved in an OpenEmbedded layer. The interesting bit
from this one is that they have 4 separate packages. I don't think we need 4,
but 2 could be useful.


 Regards,
 Arnout


[1] https://wiki.linaro.org/PeterPearse/GobjectIntrospection
[2] https://wiki.gnome.org/Projects/GObjectIntrospection/Architecture
[3] https://github.com/Guacamayo/meta-gir/blob/master/README.md
-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2017-08-17 22:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23  0:54 [Buildroot] [RFC PATCH 0/2] add gobject-introspection Sam Bobroff
2017-02-23  0:54 ` [Buildroot] [RFC PATCH 1/2] package/gobject-introspection: add package Sam Bobroff
2017-02-23  9:18   ` Thomas Petazzoni
2017-02-24  4:07     ` Sam Bobroff
2017-02-24  8:25       ` Thomas Petazzoni
2017-02-27 14:58         ` Arnout Vandecappelle
2017-02-27 15:06           ` Baruch Siach
2017-02-27 23:22             ` Sam Bobroff
2017-08-15 10:47               ` Adam Duskett
2017-08-17  6:44                 ` Alexey Roslyakov
2017-08-17 22:39                   ` Arnout Vandecappelle [this message]
2017-08-22 10:57                     ` Adam Duskett
2017-08-24 23:03                       ` Arnout Vandecappelle
2017-08-26 16:01                         ` Adam Duskett
2017-08-27  5:11                           ` Waldemar Brodkorb
2017-08-27 15:15                             ` Adam Duskett
2017-02-27 15:58           ` Thomas Petazzoni
2017-02-27 22:54             ` Sam Bobroff
2017-02-23 13:02   ` Baruch Siach
2017-02-23 13:44   ` Jérôme Pouiller
2017-02-23  0:54 ` [Buildroot] [RFC PATCH 2/2] package/libvips: enable introspection Sam Bobroff
2017-02-23  9:19   ` Thomas Petazzoni

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=346fcaef-6d03-4d57-c749-da966016d401@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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.