All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 1/2] package/gobject-introspection: add package
Date: Mon, 27 Feb 2017 17:06:37 +0200	[thread overview]
Message-ID: <20170227150637.ljo2c6dv3izstddn@tarshish> (raw)
In-Reply-To: <8eeadd56-4c2b-94ff-c182-50e18e81f749@mind.be>

Hi Arnout,

On Mon, Feb 27, 2017 at 03:58:54PM +0100, Arnout Vandecappelle wrote:
> On 24-02-17 09:25, Thomas Petazzoni wrote:
> > On Fri, 24 Feb 2017 15:07:13 +1100, Sam Bobroff wrote:
> > 
> >> Yes, absolutely, and I really don't know how we should handle it. I
> >> searched fairly hard for another solution but the only other one seems
> >> to be to rewrite gobject-introspection completely and the other
> >> projects that have attempted this have used the same host-qemu approach
> >> (that's yocto and cygwin).
> > Can you summarize what is Qemu used for in the context of building
> > gobject-introspection ?
> > 
> > If it's to generate some architecture-specific file, can we
> > pre-generate it, and bundle it with Buildroot ?
> 
>  As far as I can see, it just runs ldd under qemu, to find the paths to the
> libraries that will actually be used (i.e., the libraries that have to be
> introspected, I guess). That's why Jerome suggested to use his cross-ldd
> scriptlet [1], which would also work with musl and uClibc.
> 
>  However, as far as I understand, it really only needs to find a list of shared
> libraries used by a program. In our case, instead of going through ldd, we can
> just use readelf because there is normally only a single instance of each SONAME
> in the target.

My understanding is that the process is more involved than that. Quoting the 
Yocto summary[1]:

  The data is generated when building such a library, by linking the library 
  with a small executable binary that asks the library to describe itself, 
  then executing the binary and processing its output.

I didn't verify this myself yet.

[1] https://lists.yoctoproject.org/pipermail/yocto/2016-April/029579.html

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

  reply	other threads:[~2017-02-27 15:06 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 [this message]
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
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=20170227150637.ljo2c6dv3izstddn@tarshish \
    --to=baruch@tkos.co.il \
    --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.