Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package:	multimedia/alsa-lib python
Date: Mon, 26 Jan 2009 20:01:02 +0100	[thread overview]
Message-ID: <1232996462.2298.93.camel@elrond.atmel.com> (raw)
In-Reply-To: <87vds26pot.fsf@macbook.be.48ers.dk>

m?n 2009-01-26 klockan 16:40 +0100 skrev Peter Korsgaard:
> >>>>> "Peter" == Peter Korsgaard <jacmet@uclibc.org> writes:
> 
>  ulf> http://www.alsa-project.org/
>  ulf> +
>  ulf> +config BR2_PACKAGE_ALSA_LIB_PYTHON
>  ulf> +	bool "Python support for alsa-lib"
>  ulf> +	depends on BR2_PACKAGE_ALSA_LIB
>  ulf> +	select BR2_PACKAGE_PYTHON
> 
>  Peter> It would probably be goodt to add a 'default BR2_PACKAGE_PYTHON' line,
>  Peter> so it defaults to enabled if you have python support, and false
>  Peter> otherwise.
> 
>  Peter> Alternatively it should depend on BR2_PACKAGE_PYTHON and just be
>  Peter> default y, as it's probably pretty unlikely someone wants python
>  Peter> support in alsa without having python enabled in the first place.
> 
>  Peter> The 2nd option seems cleanest to me, what do you think?
> 

I think feedback was that people would like the option to build alsa-lib
WITHOUT python support even if python was on the target.
Adding python to alsa-lib means a fat library is added to the fs.

BR
Ulf Samuelsson

      reply	other threads:[~2009-01-26 19:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-17  0:19 [Buildroot] svn commit: trunk/buildroot/package: multimedia/alsa-lib python ulf at uclibc.org
2009-01-17  7:54 ` Peter Korsgaard
2009-01-26 15:40   ` Peter Korsgaard
2009-01-26 19:01     ` Ulf Samuelsson [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=1232996462.2298.93.camel@elrond.atmel.com \
    --to=ulf.samuelsson@atmel.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