Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: aduskett at gmail.com <aduskett@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/libostree: add introspection support
Date: Fri, 20 Mar 2020 15:23:59 -0700	[thread overview]
Message-ID: <20200320222359.88689-2-aduskett@gmail.com> (raw)
In-Reply-To: <20200320222359.88689-1-aduskett@gmail.com>

From: Adam Duskett <Aduskett@gmail.com>

If gobject-introspection is selected, explicitly set --enable-introspection in
the configure options and add a dependency for gobject-introspection.

Signed-off-by: Adam Duskett <Aduskett@gmail.com>
---
 package/libostree/libostree.mk | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/package/libostree/libostree.mk b/package/libostree/libostree.mk
index bdbe6b5aba..63e6bbfde3 100644
--- a/package/libostree/libostree.mk
+++ b/package/libostree/libostree.mk
@@ -30,6 +30,13 @@ else
 LIBOSTREE_CONF_OPTS += --without-openssl
 endif
 
+ifeq ($(BR2_PACKAGE_GOBJECT_INTROSPECTION),y)
+LIBOSTREE_CONF_OPTS += --enable-introspection
+LIBOSTREE_DEPENDENCIES += gobject-introspection
+else
+LIBOSTREE_CONF_OPTS += --disable-introspection
+endif
+
 # Avahi support needs libavahi-client, which is built by avahi if avahi-daemon
 # and dbus is selected. Since there is no BR2_PACKAGE_LIBAVAHI_CLIENT config
 # option yet, use the avahi-daemon and dbus config symbols to check for
-- 
2.25.1

  reply	other threads:[~2020-03-20 22:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20 22:23 [Buildroot] [PATCH 1/2] package/gobject-introspection/g-ir-scanner: do not set default compiler values aduskett at gmail.com
2020-03-20 22:23 ` aduskett at gmail.com [this message]
2020-03-22  9:31   ` [Buildroot] [PATCH 2/2] package/libostree: add introspection support Yann E. MORIN
2020-03-21 21:47 ` [Buildroot] [PATCH 1/2] package/gobject-introspection/g-ir-scanner: do not set default compiler values Yann E. MORIN
2020-03-22 21:53   ` 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=20200320222359.88689-2-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