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 what version of ALSA was installed by the person that built the binary (which is usually not the same person), and won't follow dynamic library upgrades. Also, even if ALSA development files are installed, there's always a chance there's a mismatch; for example, there may be one version of ALSA in /usr/lib and another in /usr/local/lib. I want to know what real version of libasound.so the application is linked against, without having to worry about user error or unusual configurations resulting in incorrect output. This is why many libraries export a function to return the version in use: png_access_version_number, png_get_libpng_ver, zlibVersion(), SDL_Linked_Version(), confstr(_CS_GNU_LIBC_VERSION), and so on. -- Glenn Maynard ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
