From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/python-pyalsa: new package
Date: Sun, 19 Apr 2020 22:18:48 +0200 [thread overview]
Message-ID: <20200419221848.616e101f@windsurf.home> (raw)
In-Reply-To: <20200104155902.10810-1-juju@cotds.org>
On Sat, 4 Jan 2020 16:59:02 +0100
Julien Olivain <juju@cotds.org> wrote:
> Official ALSA Python binding, including hardware
> management, mixer and sequencer control.
>
> http://www.alsa-project.org/
>
> Signed-off-by: Julien Olivain <juju@cotds.org>
Thanks, I've applied. There was however one significant issue, see
below.
> diff --git a/package/python-pyalsa/Config.in b/package/python-pyalsa/Config.in
> new file mode 100644
> index 0000000000..f379096058
> --- /dev/null
> +++ b/package/python-pyalsa/Config.in
> @@ -0,0 +1,7 @@
> +config BR2_PACKAGE_PYTHON_PYALSA
> + bool "python-pyalsa"
You forgot to select BR2_PACKAGE_ALSA_LIB, and some of its sub-options,
which are needed for this package to build.
> +PYTHON_PYALSA_VERSION = 1.1.6
> +PYTHON_PYALSA_SOURCE = pyalsa-$(PYTHON_PYALSA_VERSION).tar.bz2
> +PYTHON_PYALSA_SITE = ftp://ftp.alsa-project.org/pub/pyalsa
> +PYTHON_PYALSA_SETUP_TYPE = distutils
> +PYTHON_PYALSA_LICENSE = LGPL-2.1+
And you forgot to add "alsa-lib" to PYTHON_PYALSA_DEPENDENCIES.
I fixed these issues, and applied to master. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-04-19 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 17:40 [Buildroot] [PATCH 1/1] package/python-pyalsa: new package Julien Olivain
2019-12-31 17:48 ` Baruch Siach
2020-01-04 15:59 ` [Buildroot] [PATCH v2 " Julien Olivain
2020-04-19 20:18 ` 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=20200419221848.616e101f@windsurf.home \
--to=thomas.petazzoni@bootlin.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