At Tue, 1 Jul 2003 16:52:48 -0400,
Fred Gleason wrote:
>
> On Monday 30 June 2003 09:26, Takashi Iwai wrote:
>
> > > Good idea.
> > > how about /usr/include/asihpi/hpi.h
> >
> > well, assuming the certain header location is not recommended.
> >
> > basically, the kernel sources must not refer to the standard header
> > files for user-space. if you need a header file for the kernel,
> > include it in the kernel tree. or, more easily, specify the header
> > path explicitly with -I option in Makefile (which may be given by the
> > configure script).
>
> Then perhaps '/usr/include/linux/hpi.h'.
the problem is that you cannot assume that the driver source accepts
the "standard" header-file locations, namely, /usr/include, etc.
these locations should not be referred by the kernel sources.
all header files for the kernel codes should be private.
in the case of alsa-driver package, this is not strictly prohibited.
but it's better to avoid assume the fixed location.
so, as i suggested, it's better to have an option, such as
% ./configure --with-hpi=/usr/local/src/hpi
so that the configure script can check the location of hpi.h and
enable the compilation of asihpi driver only when it's found.
i have no objection to /usr/include/asihpi/hpi.h, btw. it's just the
matter of alsa-driver side.
Takashi
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
