All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: John Keeping <john@metanate.com>
Cc: Pierre-Jean Texier <texier.pj2@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/sbc: add config option to control tools build
Date: Mon, 14 Nov 2022 23:07:04 +0100	[thread overview]
Message-ID: <20221114230704.2dda05d4@windsurf> (raw)
In-Reply-To: <20221020121521.2041129-1-john@metanate.com>

On Thu, 20 Oct 2022 13:15:21 +0100
John Keeping <john@metanate.com> wrote:

> libsndfile is only needed by the sbctester utility and the library can
> be built without this dependency.
> 
> Add a config option to cover not just sbctester but the command-line
> utilities as well.  While the utilities may be useful for debugging,
> normal usage will only need libsbc and these applications can be
> omitted.
> 
> Signed-off-by: John Keeping <john@metanate.com>
> ---
> v2:
> - Fix autocomplete error in select BR2_PACKAGE_LIBSNDFILE

I've applied to next after:

 - Moving the option inside a if BR2_PACKAGE_SBC..endif block instead
   of using a depends on BR2_PACKAGE_SBC

 - Adjusting SBC_LICENSE so that it only contains LGPL-2.1+ by default,
   and then has GPL-2.0+ in addition when the tools are built.

Thanks!

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

      reply	other threads:[~2022-11-14 22:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 12:15 [Buildroot] [PATCH v2] package/sbc: add config option to control tools build John Keeping
2022-11-14 22:07 ` Thomas Petazzoni via buildroot [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=20221114230704.2dda05d4@windsurf \
    --to=buildroot@buildroot.org \
    --cc=john@metanate.com \
    --cc=texier.pj2@gmail.com \
    --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.