From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] openal: New package
Date: Sun, 04 Oct 2015 10:12:40 +0200 [thread overview]
Message-ID: <ok37ecxrt1.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 56100EB1.4010100@dawncrow.de
Hi Andr?,
several months ago I started hacking an openal package myself but
never finished it. Here I will compare my package to your version.
Am Sat, 03 Oct 2015 19:21:53 +0200 schrieb Andr? Hentschel:
> diff --git a/package/openal/Config.in b/package/openal/Config.in
> new file mode 100644
> index 0000000..8eb177b
> --- /dev/null
> +++ b/package/openal/Config.in
> @@ -0,0 +1,16 @@
> +config BR2_PACKAGE_OPENAL
> + bool "openal"
> + # OpenAL needs a backend
> + depends on BR2_PACKAGE_ALSA_LIB || \
> + BR2_PACKAGE_PORTAUDIO || \
> + BR2_PACKAGE_PULSEAUDIO
> + help
> + OpenAL provides capabilities for playing audio in a virtual
> + 3D environment. Distance attenuation, doppler shift, and
> + directional sound emitters are among the features handled by
> + the API.
> +
> +comment "openal needs a backend"
> + depends on !BR2_PACKAGE_ALSA_LIB && \
> + !BR2_PACKAGE_PORTAUDIO && \
> + !BR2_PACKAGE_PULSEAUDIO
What about having a choice option defaulting to, for example, alsa?
Please add
http://kcat.strangesoft.net/openal.html
to Config.in. Openal also needs this
depends on BR2_TOOLCHAIN_HAS_THREADS
comment "openal needs a toolchain w/ threads"
depends on !BR2_TOOLCHAIN_HAS_THREADS
Did you test a static build? I have this in openal.mk:
ifeq ($(BR2_STATIC_LIBS),y)
OPENAL_CONF_OPTS += -DLIBTYPE=STATIC
endif
Regards, Bernd
next prev parent reply other threads:[~2015-10-04 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 17:21 [Buildroot] [PATCH] openal: New package André Hentschel
2015-10-04 8:12 ` Bernd Kuhls [this message]
2015-10-04 17:04 ` André Hentschel
-- strict thread matches above, loose matches on Subject: below --
2015-10-12 19:32 André Hentschel
2015-10-12 19:47 ` Thomas Petazzoni
2015-10-13 17:07 ` Vicente Olivert Riera
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=ok37ecxrt1.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 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.