From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] caps: new package
Date: Mon, 4 Aug 2014 22:28:55 +0200 [thread overview]
Message-ID: <20140804222855.6cb14837@free-electrons.com> (raw)
In-Reply-To: <1398374384-8814-2-git-send-email-martin@barkynet.com>
Dear Martin Bark,
Thanks for your contribution, and sorry for the slow feedback. Some
comments below.
On Thu, 24 Apr 2014 22:19:43 +0100, Martin Bark wrote:
> diff --git a/package/Config.in b/package/Config.in
> index 5956154..33d16ac 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -491,6 +491,7 @@ menu "Libraries"
> menu "Audio/Sound"
> source "package/alsa-lib/Config.in"
> source "package/audiofile/Config.in"
> +source "package/caps/Config.in"
This will have to be rebased on top of the latest master.
> new file mode 100644
> index 0000000..28ff332
> --- /dev/null
> +++ b/package/caps/Config.in
> @@ -0,0 +1,12 @@
> +config BR2_PACKAGE_CAPS
> + bool "caps"
Missing dependency on C++ in toolchain. Also, this package uses
ladspa.h, so surely it should select BR2_PACKAGE_LADSPA_SDK, no?
> diff --git a/package/caps/caps-01-cross-compile-fix.patch b/package/caps/caps-01-cross-compile-fix.patch
> new file mode 100644
> index 0000000..4667191
> --- /dev/null
> +++ b/package/caps/caps-01-cross-compile-fix.patch
Missing description + Signed-off-by line.
> diff --git a/package/caps/caps.mk b/package/caps/caps.mk
> new file mode 100644
> index 0000000..d642bc8
> --- /dev/null
> +++ b/package/caps/caps.mk
> @@ -0,0 +1,21 @@
> +################################################################################
> +#
> +# caps
> +#
> +################################################################################
> +
> +CAPS_VERSION = 0.9.23
> +CAPS_SOURCE = caps_$(CAPS_VERSION).tar.bz2
> +CAPS_SITE = http://quitte.de/dsp/
> +CAPS_LICENSE = GPLv3
> +CAPS_LICENSE_FILES = COPYING
CAPS_DEPENDENCIES = ladspa-sdk
maybe ?
> +
> +define CAPS_BUILD_CMDS
> + $(TARGET_CONFIGURE_OPTS) $(MAKE) -C $(@D) all
We normally try to pass $(TARGET_CONFIGURE_OPTS) on the right hand side
of $(MAKE), and we pass $(TARGET_MAKE_ENV) on the left hand side of
make.
> +define CAPS_INSTALL_TARGET_CMDS
> + $(MAKE) -C $(@D) install DESTDIR=$(TARGET_DIR)
$(TARGET_MAKE_ENV) on the left hand side, and DESTDIR passed before
'install' would be preferred here.
Otherwise, looks good.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-08-04 20:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 21:19 [Buildroot] [PATCH 1/3] ladspa-sdk: new package Martin Bark
2014-04-24 21:19 ` [Buildroot] [PATCH 2/3] caps: " Martin Bark
2014-08-04 20:28 ` Thomas Petazzoni [this message]
2014-08-05 20:51 ` Martin Bark
2014-04-24 21:19 ` [Buildroot] [PATCH 3/3] alsaequal: " Martin Bark
2014-08-04 20:32 ` Thomas Petazzoni
2014-08-05 20:52 ` Martin Bark
2014-08-06 8:00 ` Thomas Petazzoni
2014-08-04 20:23 ` [Buildroot] [PATCH 1/3] ladspa-sdk: " Thomas Petazzoni
2014-08-05 20:50 ` Martin Bark
2014-08-06 7:59 ` Thomas Petazzoni
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=20140804222855.6cb14837@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 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.