From: aduskett at gmail.com <aduskett@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] package/gobject-introspection: fix meson support
Date: Fri, 21 Feb 2020 14:43:10 -0800 [thread overview]
Message-ID: <20200221224313.854089-1-aduskett@gmail.com> (raw)
From: Adam Duskett <Aduskett@gmail.com>
This patch series addresses two remaining issues with gobject-introspection.
1) host-goi doesn't build .typelib or .gir files. These missing files can be
an issue when there is a host package that requires introspection, but
they are missing.
2) Meson doesn't work due to linking issues.
This patch series fixes both issues.
Patch 1 exports LD_LIBRARY_PATH when building host-gobject-introspection,
which allows GOI to link against the hosts libglib2 library.
Patch 2 explicitly exports CC in g-ir-scanner.in.
Patch 3 adds g-ir-scanner and g-ir-compiler paths to cross-compilation.conf.in
I tested this patch with a few autotools packages and with gstreamer1, and it
works quite well!
Adam Duskett (3):
package/gobject-introspection: fix host-linking
package/gobject-introspection: export cc in g-ir-scanner
package/meson: add gobject-introspection tools to
cross-compilation.conf.in
package/gobject-introspection/g-ir-scanner.in | 2 ++
.../gobject-introspection/gobject-introspection.mk | 12 +++++++-----
package/meson/cross-compilation.conf.in | 2 ++
3 files changed, 11 insertions(+), 5 deletions(-)
--
2.24.1
next reply other threads:[~2020-02-21 22:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 22:43 aduskett at gmail.com [this message]
2020-02-21 22:43 ` [Buildroot] [PATCH 1/3] package/gobject-introspection: fix host-linking aduskett at gmail.com
2020-02-23 20:41 ` Yann E. MORIN
2020-02-21 22:43 ` [Buildroot] [PATCH 2/3] package/gobject-introspection: export cc in g-ir-scanner aduskett at gmail.com
2020-02-23 20:45 ` Yann E. MORIN
2020-02-21 22:43 ` [Buildroot] [PATCH 3/3] package/meson: add gobject-introspection tools to cross-compilation.conf.in aduskett at gmail.com
2020-02-23 20:58 ` Yann E. MORIN
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=20200221224313.854089-1-aduskett@gmail.com \
--to=aduskett@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox