On Tue, Apr 06, 2004 at 11:16:17PM +0100, James Courtier-Dutton wrote:
> cat /usr/include/alsa/version.h tells you the currently installed version.
Nope. That only works if the development files are installed; on user
systems, they usually aren't. I can't simply #include it; that'll tell
me wha
Glenn Maynard wrote:
On Tue, Apr 06, 2004 at 05:04:34PM -0400, Paul Davis wrote:
I can't find any way to detect the running ALSA version, for diagnostic
cat /proc/asound/version
That's the driver version, which I'm already logging. Like I said, I
want the alsa-lib version that's being linked in
>I can't find any way to detect the running ALSA version, for diagnostic
cat /proc/asound/version
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologi
On Tue, Apr 06, 2004 at 05:04:34PM -0400, Paul Davis wrote:
> >I can't find any way to detect the running ALSA version, for diagnostic
>
> cat /proc/asound/version
That's the driver version, which I'm already logging. Like I said, I
want the alsa-lib version that's being linked in, which very of
I can't find any way to detect the running ALSA version, for diagnostic
purposes. It can't be derived from the library name, which doesn't seem
to change (it's always "libasound.so.2.0.0" here, which has no relation
to the actual version).
It's frustrating to receive bug reports like
https://s
