All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Nicolas Cavallari <nicolas.cavallari@green-communications.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/bluez-alsa: bump version to 4.3.1
Date: Tue, 3 Sep 2024 22:26:50 +0200	[thread overview]
Message-ID: <20240903222650.10afba32@windsurf> (raw)
In-Reply-To: <20240903160038.19535-2-nicolas.cavallari@green-communications.fr>

On Tue,  3 Sep 2024 18:00:31 +0200
Nicolas Cavallari <nicolas.cavallari@green-communications.fr> wrote:

> Add new optional dependencies on bluez midi support, opus, systemd and
> spandsp.

We need your Signed-off-by line.

> ---
>  package/bluez-alsa/bluez-alsa.hash |  2 +-
>  package/bluez-alsa/bluez-alsa.mk   | 30 +++++++++++++++++++++++++++++-
>  2 files changed, 30 insertions(+), 2 deletions(-)
> 
> diff --git a/package/bluez-alsa/bluez-alsa.hash b/package/bluez-alsa/bluez-alsa.hash
> index 5513865603..fbcbabea28 100644
> --- a/package/bluez-alsa/bluez-alsa.hash
> +++ b/package/bluez-alsa/bluez-alsa.hash
> @@ -1,3 +1,3 @@
>  # Locally calculated:
> -sha256  b69a3e6dd69315194403ee930ac1553aed3fb9a3988e502ae5c24a8bfef70f9f  bluez-alsa-4.1.1.tar.gz
> +sha256  933fe898dfac21fdfeb5f4ffa685c2aa2db9c064d639170ac2652f156e956a2a  bluez-alsa-4.3.1.tar.gz
>  sha256  956564dcf06ba65cd7a5eb6cdfd695e2ab0f09ea9684e4eaf079f5d533bd206d  LICENSE
> diff --git a/package/bluez-alsa/bluez-alsa.mk b/package/bluez-alsa/bluez-alsa.mk
> index 38682c2755..8a5abe3f7f 100644
> --- a/package/bluez-alsa/bluez-alsa.mk
> +++ b/package/bluez-alsa/bluez-alsa.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -BLUEZ_ALSA_VERSION = 4.1.1
> +BLUEZ_ALSA_VERSION = 4.3.1
>  BLUEZ_ALSA_SITE = $(call github,Arkq,bluez-alsa,v$(BLUEZ_ALSA_VERSION))
>  BLUEZ_ALSA_LICENSE = MIT
>  BLUEZ_ALSA_LICENSE_FILES = LICENSE
> @@ -16,6 +16,7 @@ BLUEZ_ALSA_AUTORECONF = YES
>  BLUEZ_ALSA_CONF_OPTS = \
>  	--enable-a2dpconf \
>  	--enable-aplay \
> +	--enable-cli \
>  	--disable-debug-time \
>  	--with-alsaplugindir=/usr/lib/alsa-lib \
>  	--with-alsaconfdir=/etc/alsa/conf.d
> @@ -73,6 +74,12 @@ else
>  BLUEZ_ALSA_CONF_OPTS += --disable-rfcomm
>  endif
>  
> +ifeq ($(BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_MIDI),y)
> +BLUEZ_ALSA_CONF_OPTS += --enable-midi
> +else
> +BLUEZ_ALSA_CONF_OPTS += --disable-midi
> +endif

Maybe group with the other conditions testing
BR2_PACKAGE_BLUEZ5_UTILS_* options in the same file?

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-09-03 20:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 16:00 [Buildroot] [PATCH 1/2] DEVELOPERS: add bluez-alsa to myself Nicolas Cavallari
2024-09-03 16:00 ` [Buildroot] [PATCH 2/2] package/bluez-alsa: bump version to 4.3.1 Nicolas Cavallari
2024-09-03 20:26   ` Thomas Petazzoni via buildroot [this message]
2024-09-04  8:05     ` Nicolas Cavallari
2024-09-03 20:24 ` [Buildroot] [PATCH 1/2] DEVELOPERS: add bluez-alsa to myself Thomas Petazzoni via buildroot

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=20240903222650.10afba32@windsurf \
    --to=buildroot@buildroot.org \
    --cc=nicolas.cavallari@green-communications.fr \
    --cc=thomas.petazzoni@bootlin.com \
    /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.