From: Randell Jesup <randell1@jesup.org>
To: alsa-devel@alsa-project.org
Subject: Use of _hint() functions and older machines
Date: Thu, 20 Oct 2011 23:28:37 -0400 [thread overview]
Message-ID: <4EA0E6E5.1050600@jesup.org> (raw)
[ I initially posted this to the -users list, but it may be more
appropriate here ]
At Mozilla, we're in the process of adding support for WebRTC
(http://webrtc.org/), which is being standardized by the IETF (their
part is 'rtcweb'), and the W3C. This adds real-time audio and video
(and data) communication to browsers, peer-to-peer over encrypted channels.
We have a sound library that can load either Pulse or Alsa. However,
for Alsa, it wants to look at snd_device_name_hint() and also
_get_hint() and _free_hint(). It lazy-binds to libasound, so it will
dlopen() it and then dlsym() all the symbols it uses; if any fail it
unloads the lib and says it's not there. It uses the hint functions to
build a device list, for example for presenting to the user.
I have two problems:
1) Firefox is build on machines configured with I believe Centos5, and
I'm told the machines run Alsa 1.0.12, while the hints() functions were
added in 1.0.14 (released June 2007). Right now I can't build release
or 'try' builds on the build servers because of this.
2) We'd like to run on older machines if possible, and official release
builds are made on those servers. On older machines, _hint() aren't
available, so even if I make them optional to dlsym-loading, I would
need some other method to get the information I assume using older,
now-deprecated-or-gone interfaces.
Any suggestions? Tips?
See
http://code.google.com/p/webrtc/source/browse/trunk/src/modules/audio_device/main/source/linux/audio_device_alsa_linux.cc?r=347#2348
for how they're used currently.
Thanks!
--
Randell Jesup
randell-ietf@jesup.org
next reply other threads:[~2011-10-21 3:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 3:28 Randell Jesup [this message]
2011-10-22 18:04 ` Use of _hint() functions and older machines Colin Guthrie
2011-10-23 7:46 ` Randell Jesup
2011-10-23 10:36 ` Clemens Ladisch
2011-10-24 5:19 ` Randell Jesup
2011-10-24 7:00 ` Raymond Yau
2011-10-24 10:26 ` Clemens Ladisch
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=4EA0E6E5.1050600@jesup.org \
--to=randell1@jesup.org \
--cc=alsa-devel@alsa-project.org \
/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.