From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/cwiid: add optional dependency to bluez5_utils
Date: Sun, 7 May 2017 22:16:49 +0200 [thread overview]
Message-ID: <20170507221649.132031c2@free-electrons.com> (raw)
In-Reply-To: <16e63a8d-e200-457d-bd74-01176c67d4fe@mind.be>
Hello,
On Tue, 21 Mar 2017 09:36:23 +0100, Arnout Vandecappelle wrote:
> >> - select BR2_PACKAGE_BLUEZ_UTILS
> >> + select BR2_PACKAGE_BLUEZ5_UTILS if !BR2_PACKAGE_BLUEZ_UTILS
> >
> > You need to add missing bluez5_utils dependencies
> > (BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_4, BR2_TOOLCHAIN_HAS_SYNC_4). Changing
> > bluez_utils to bluez5_utils in the comments above would also be nice.
>
> Darn, this is getting complicated... We would want to keep the dependencies as
> they are, and use bluez_utils in case bluez5_utils are not available. But that
> would mean something like:
>
> select BR2_PACKAGE_BLUEZ5_UTILS if !BR2_PACKAGE_BLUEZ_UTILS \
> && BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_4 \
> && BR2_TOOLCHAIN_HAS_SYNC_4
> select BR2_PACKAGE_BLUEZ_UTILS if !BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_4 \
> || !BR2_TOOLCHAIN_HAS_SYNC_4
>
> Yuk...
>
> Perhaps a BR2_PACKAGE_BLUEZ5_UTILS_ARCH_SUPPORTS would help?
Perhaps it's a case where we need to use a "depends on" dependency
rather than a "select" dependency, i.e do:
depends on BR2_PACKAGE_BLUEZ5_UTILS || BR2_PACKAGE_BLUEZ_UTILS
Bernd, could you resubmit your patch with this idea? Don't forget to
remove the "depends on" on toolchain/architecture features that are no
longer needed.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-05-07 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 7:22 [Buildroot] [PATCH v2 1/1] package/cwiid: add optional dependency to bluez5_utils Bernd Kuhls
2017-03-21 7:31 ` Baruch Siach
2017-03-21 8:36 ` Arnout Vandecappelle
2017-05-07 20:16 ` Thomas Petazzoni [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=20170507221649.132031c2@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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