From: Jeremy White <jwhite@codeweavers.com>
To: Jaroslav Kysela <perex@suse.cz>
Cc: alsa-devel@lists.sourceforge.net, Robert Reif <reif@earthlink.net>
Subject: Re: RFC: Appropriate device detection for Wine
Date: Tue, 07 Jun 2005 09:25:46 -0500 [thread overview]
Message-ID: <42A5AE6A.2070204@codeweavers.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0506071445070.1752@pnote.perex-int.cz>
> Yes, but you should use the new API (use dlopen/dlsym for
> snd_names_list/snd_names_list_free to let your code work with older
> alsa-lib) and provide fallback when the symbols don't exist or the list
> of devices is empty.
Fair enough; is it now the case that snd_names_list is considered
the canonical list of Alsa devices? If found, there is no need
to check environment variables or anything else?
Cheers,
Jeremy
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
next prev parent reply other threads:[~2005-06-07 14:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 3:52 RFC: Appropriate device detection for Wine Jeremy White
2005-06-07 7:32 ` Jaroslav Kysela
2005-06-07 12:27 ` Jeremy White
2005-06-07 12:48 ` Jaroslav Kysela
2005-06-07 14:25 ` Jeremy White [this message]
2005-06-13 2:43 ` RFC: Appropriate device detection for Wine (more advice needed) Jeremy White
2005-06-13 7:24 ` Clemens Ladisch
2005-06-13 12:23 ` Jeremy White
2005-06-13 12:35 ` Takashi Iwai
2005-06-13 14:00 ` Jeremy White
2005-06-13 14:23 ` Takashi Iwai
2005-06-13 15:01 ` Jeremy White
2005-06-13 15:11 ` Takashi Iwai
2005-06-14 3:22 ` Jeremy White
2005-06-14 8:30 ` Takashi Iwai
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=42A5AE6A.2070204@codeweavers.com \
--to=jwhite@codeweavers.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
--cc=reif@earthlink.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.