Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Pavel Roskin <proski@gnu.org>,
	"alsa-devel@lists.sourceforge.net"
	<alsa-devel@lists.sourceforge.net>
Subject: Re: Driver headers used by alsa-lib
Date: Wed, 09 Oct 2002 12:06:33 +0200	[thread overview]
Message-ID: <s5hy9980vva.wl@alsa2.suse.de> (raw)
In-Reply-To: <s5hznto0wdb.wl@alsa2.suse.de>

sorry, corrections:

At Wed, 09 Oct 2002 11:55:44 +0200,
I wrote:
> 
> as mentioned above, alsa-lib needs only the three header files from
> alsa-kernel.  hence the duplication is necessary only for them, and
> it's not too much.
 
also ainstr_*.h are necessary, too.

> the installation of kernel header files shall be done anyway from
> alsa-driver, so the all files will be there.  should be no problem.

it turned out that the files are included as <sound/*.h>, so
apparently we need to put the files under sound directory.

the candidate is,

1. /usr/include/alsa/kernel/sound/*.h
2. /usr/include/alsa/sound/*.h
3. /usr/include/sound/*.h	(as it is)

i'd prefer 1 since it's clear that the header files belong to the
kernel, but it's a bit too deep.

suggestions?


Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

      reply	other threads:[~2002-10-09 10:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-04 17:20 Driver headers used by alsa-lib Pavel Roskin
2002-10-04 17:48 ` Peter L Jones
2002-10-08 11:14 ` Takashi Iwai
2002-10-09  6:58   ` Jaroslav Kysela
2002-10-09  9:55     ` Takashi Iwai
2002-10-09 10:06       ` Takashi Iwai [this message]

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=s5hy9980vva.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=perex@suse.cz \
    --cc=proski@gnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox