From: Marcus Folkesson <marcus.folkesson@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libiio: fix libavahi-client dependency
Date: Wed, 27 Dec 2017 13:22:24 +0100 [thread overview]
Message-ID: <20171227122224.GB24556@gmail.com> (raw)
In-Reply-To: <20171227121249.bgyakvui5g73jsch@sapphire.tkos.co.il>
Hi Baruch,
On Wed, Dec 27, 2017 at 02:12:49PM +0200, Baruch Siach wrote:
> Hi Marcus,
>
> On Wed, Dec 27, 2017 at 01:06:03PM +0100, Marcus Folkesson wrote:
> > Avahi needs avahi-daemon and D-Bus to build avahi-client.
> >
> > Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
> > ---
> > package/libiio/libiio.mk | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/package/libiio/libiio.mk b/package/libiio/libiio.mk
> > index 0b13064085..0ff6c47dba 100644
> > --- a/package/libiio/libiio.mk
> > +++ b/package/libiio/libiio.mk
> > @@ -54,8 +54,8 @@ else
> > LIBIIO_CONF_OPTS += -DWITH_IIOD_USBD=OFF
> > endif
> >
> > -# Avahi support in libiio requires avahi-client, which needs avahi-daemon
> > -ifeq ($(BR2_PACKAGE_AVAHI)$(BR2_PACKAGE_AVAHI_DAEMON),yy)
> > +# Avahi support in libiio requires avahi-client, which needs avahi-daemon and dbus
> > +ifeq ($(BR2_PACKAGE_AVAHI)$(BR2_PACKAGE_AVAHI_DAEMON)$(BR2_PACKAGE_DBUS),yyy)
>
> When BR2_PACKAGE_AVAHI_DAEMON is enabled, BR2_PACKAGE_AVAHI must also be
> enabled. So the is no need to check for BR2_PACKAGE_AVAHI.
>
You are so right.
> > LIBIIO_DEPENDENCIES += avahi
> > endif
>
> baruch
>
> --
> http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
> =}------------------------------------------------ooO--U--Ooo------------{=
> - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
Best regards
Marcus Folkesson
prev parent reply other threads:[~2017-12-27 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-27 12:06 [Buildroot] [PATCH] libiio: fix libavahi-client dependency Marcus Folkesson
2017-12-27 12:12 ` Baruch Siach
2017-12-27 12:22 ` Marcus Folkesson [this message]
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=20171227122224.GB24556@gmail.com \
--to=marcus.folkesson@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