From: Takashi Iwai <tiwai@suse.de>
To: Patrick Welche <prlw1@cam.ac.uk>
Cc: alsa-devel@alsa-project.org, Clemens Ladisch <clemens@ladisch.de>
Subject: Re: alsa on non-linux
Date: Wed, 26 Feb 2014 08:20:07 +0100 [thread overview]
Message-ID: <s5hd2iauyqg.wl%tiwai@suse.de> (raw)
In-Reply-To: <20140225124514.GB23368@quantz>
At Tue, 25 Feb 2014 12:45:14 +0000,
Patrick Welche wrote:
>
> On Thu, Jan 16, 2014 at 02:46:52PM +0100, Takashi Iwai wrote:
> > At Thu, 16 Jan 2014 13:27:17 +0000,
> > Patrick Welche wrote:
> > Why excluding hwdep...? And, no, the codes have been written to be
> > portable, but the primary goal is a thin layer for Linux kernel ABI,
> > thus its support is the highest priority.
> >
> > The linux/*.h file inclusions are basically for allowing to include
> > sound/asound.h as is. It's a part of the Linux kernel code, and I
> > don't think we'd add any extra ifdefs there just for non-Linux.
> >
> > IOW, you'd need to prepare some compatible defines before including
> > sound/asound.h if you need to compile for non-Linux systems.
>
> I should have read this more carefully before preparing the attached
> patch... I changed asound.h.
>
> The attached is what I needed to be able to build with
>
> ../configure --prefix=/tmp \
> --enable-debug \
> --disable-resmgr \
> --disable-aload \
> --disable-mixer \
> --disable-pcm \
> --disable-rawmidi \
> --disable-hwdep \
> --disable-seq \
> --disable-ucm \
> --disable-alisp \
> --disable-old-symbols \
> --disable-python \
> --with-debug \
> --without-libdl \
> --without-librt
>
> so not very useful, but at least it compiles.
> (This is on top of 0001-autotools-update-style.patch)
This isn't a way I supposed. In principle, you must not touch
include/sound/*.h files. These are just copies from Linux kernel
tree, thus they are managed there.
For any lacking linux/*.h files, you can create the own in somewhere
locally by detecting in configure script. For example, keep a
directory include-compat/linux/types.h, and add -Iinclude-compat for
non-Linux systems.
Takashi
prev parent reply other threads:[~2014-02-26 7:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 15:37 alsa on non-linux Patrick Welche
2014-01-13 12:13 ` Takashi Iwai
2014-01-14 10:17 ` Patrick Welche
2014-01-14 13:23 ` Takashi Iwai
2014-02-21 1:27 ` Patrick Welche
2014-02-21 11:04 ` Takashi Iwai
2014-02-23 11:12 ` Patrick Welche
2014-02-24 10:03 ` Takashi Iwai
2014-02-25 12:40 ` Patrick Welche
2014-02-26 7:17 ` Takashi Iwai
2014-01-14 14:04 ` Clemens Ladisch
2014-01-16 13:27 ` Patrick Welche
2014-01-16 13:46 ` Takashi Iwai
2014-02-25 12:45 ` Patrick Welche
2014-02-26 7:20 ` 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=s5hd2iauyqg.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=prlw1@cam.ac.uk \
/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