On Tue, 11 Sep 2001, Takashi Iwai wrote:
> At Tue, 11 Sep 2001 10:01:36 +0200 (CEST),
> Alexander Ehlert wrote:
> >
> > Hi,
> >
> > > No, /usr/include/sound/* belong only to kernel stuffs, and
> >
> > yeah sure, thats what I said.
> >
> > > sys/asoundlib.h is for API. For compiling usual apps, you don't have
> >
> > Exactly, but I just wanted to point out that sys is not the right location
> > to put asoundlib.h. Because all other files in there belong to the kernel
> > API, whereas asoundlib.h is ALSA's API for the alsa-lib. So why not put
> > that headerfile in /usr/include/sound as well.
> > Or better /usr/include/alsa. And leave it with that location. It's bad
> > enough that the ALSA API is constantly changing, so why start
> > changing locations. I already have ifdefs for ALSA 0.5.x and ALSA 0.9.x
> > in my code. I don't want to ifdef different versions of 0.9.
>
> Looks like you convinced Jaroslav, judging from the latest cvs changes
> :)
It's true that the location of asoundlib.h was based on the historical
reasons where the library was not completely independent on the ALSA
driver. Now, when we can easily write user space drivers without any pain,
we can change the official location.
> I agree also that /usr/include/alsa is better place to go, except for
> (again) compile problem. How about to put a single line header
> '#include <alsa/soundlib.h>' to sys/asoundlib.h to keep away from
> thousands bugreports?
Done.
Jaroslav
-----
Jaroslav Kysela <[EMAIL PROTECTED]>
SuSE Linux http://www.suse.com
ALSA project http://www.alsa-project.org
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
