All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/shairport-sync: bump to version 2.4
Date: Mon, 7 Sep 2015 21:15:41 +0300	[thread overview]
Message-ID: <20150907181541.GJ2213@tarshish> (raw)
In-Reply-To: <1441639190-7447-1-git-send-email-joerg.krause@embedded.rocks>

Hi J?rg,

On Mon, Sep 07, 2015 at 05:19:50PM +0200, J?rg Krause wrote:
> Version 2.4 of shairport-sync introduces new optional features (metadata,
> stdout, pipe) which we enable by default. The impact on the binary size is
> about 18 kB (110 kB vs 92 kB) for an ARM target.
> 
> Also add a new dependency to libconfig and install the default config script.
> 
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
>  package/shairport-sync/Config.in         | 1 +
>  package/shairport-sync/shairport-sync.mk | 9 +++++++--
>  2 files changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/package/shairport-sync/Config.in b/package/shairport-sync/Config.in
> index c1d81a7..c558a64 100644
> --- a/package/shairport-sync/Config.in
> +++ b/package/shairport-sync/Config.in
> @@ -4,6 +4,7 @@ config BR2_PACKAGE_SHAIRPORT_SYNC
>  	depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL
>  	select BR2_PACKAGE_ALSA_LIB
>  	select BR2_PACKAGE_ALSA_LIB_MIXER
> +	select BR2_PACKAGE_LIBCONFIG

Isn't that a build time dependency? If so, please add to 
SHAIRPORT_SYNC_DEPENDENCIES as well.

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 -

      reply	other threads:[~2015-09-07 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-07 15:19 [Buildroot] [PATCH 1/1] package/shairport-sync: bump to version 2.4 Jörg Krause
2015-09-07 18:15 ` Baruch Siach [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=20150907181541.GJ2213@tarshish \
    --to=baruch@tkos.co.il \
    --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 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.