Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 13/14] package/jack2: add optional support for opus
Date: Sun, 21 Feb 2016 12:03:42 +0100	[thread overview]
Message-ID: <e5iopcx3h.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 56C996A2.2080108@mind.be

Hi Arnout,

Am Sun, 21 Feb 2016 11:51:14 +0100 schrieb Arnout Vandecappelle:

>  Note that it also seems to have an optional dependency on celt051,
>  dbus,
> libsndfile, libsamplerate (based on looking at the wscripts).

Quoting https://git.busybox.net/buildroot/tree/package/jack2/jack2.mk#n10
"JACK2_DEPENDENCIES = libsamplerate libsndfile alsa-lib host-python"

I tried to compile celt051 with jack2 but somehow celt051 was not 
detected by jack2.

>  Which makes me wonder: how did you find these optional dependencies? I
>  assumed
> that you had built an allyesconfig, then deleted output/build, then
> built again,
> and then did a readelf. But in that case, you should have caught these
> other dependencies.

I built an allyesconfig, but the dependency check was done by the fli4l
[1] build system. Fli4l uses buildroot to compile its binaries but it 
extends buildroot by a sandbox mechanism. Before installing binaries to 
staging and target dirs all packages are installed into a package-
specific sandbox directory first, in this directory all linked libraries 
of the package binaries are detected and checked whether they are part of 
<pkg>_DEPENDENCIES, if not, the build fails.

The list of packages I talked about[2] was gathered that way, so there is 
no guarantee I caught all dependencies, the same is true for the method 
you described. Thats the reason I did not bother much about the missing 
celt051 detection by jack2.

Btw, fli4l uses the top-level parallel make option ;)

Regards, Bernd

[1] http://www.fli4l.de/en/home/whats-that-fli4l/
[2] http://article.gmane.org/gmane.comp.lib.uclibc.buildroot/139935

  reply	other threads:[~2016-02-21 11:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-21  9:50 [Buildroot] [PATCH 01/14] package/patch: add optional support for attr Bernd Kuhls
2016-02-21  9:50 ` [Buildroot] [PATCH 02/14] package/libglib2: add optional support for elfutils Bernd Kuhls
2016-02-21  9:50 ` [Buildroot] [PATCH 03/14] package/pure-ftpd: " Bernd Kuhls
2016-02-21  9:50 ` [Buildroot] [PATCH 04/14] package/iproute2: " Bernd Kuhls
2016-02-21  9:50 ` [Buildroot] [PATCH 05/14] package/openipmi: add optional support for gdbm Bernd Kuhls
2016-02-21  9:50 ` [Buildroot] [PATCH 06/14] package/zsh: " Bernd Kuhls
2016-02-21  9:50 ` [Buildroot] [PATCH 07/14] package/zsh: add optional support for libcap Bernd Kuhls
2016-02-21  9:50 ` [Buildroot] [PATCH 08/14] package/zsh: add optional support for pcre Bernd Kuhls
2016-02-21  9:50 ` [Buildroot] [PATCH 09/14] package/pulseaudio: add optional support for gdbm Bernd Kuhls
2016-02-21  9:50 ` [Buildroot] [PATCH 10/14] package/pulseaudio: add optional support for jack2 Bernd Kuhls
2016-02-21  9:50 ` [Buildroot] [PATCH 11/14] package/pulseaudio: add optional support for libsoxr Bernd Kuhls
2016-02-21  9:50 ` [Buildroot] [PATCH 12/14] package/pulseaudio: add optional support for udev Bernd Kuhls
2016-02-21 11:48   ` Thomas Petazzoni
2016-02-21  9:50 ` [Buildroot] [PATCH 13/14] package/jack2: add optional support for opus Bernd Kuhls
2016-02-21 10:51   ` Arnout Vandecappelle
2016-02-21 11:03     ` Bernd Kuhls [this message]
2016-02-21 12:43       ` Yann E. MORIN
2016-02-21  9:50 ` [Buildroot] [PATCH 14/14] package/jack2: add optional support for readline Bernd Kuhls
2016-02-21 11:47 ` [Buildroot] [PATCH 01/14] package/patch: add optional support for attr 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=e5iopcx3h.ln2@ID-313208.user.individual.net \
    --to=bernd.kuhls@t-online.de \
    --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