Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Will Wagner <will_wagner@carallon.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: alsa-utils compile issues
Date: Thu, 29 Jan 2009 15:45:57 +0100	[thread overview]
Message-ID: <s5hab9atbkq.wl%tiwai@suse.de> (raw)
In-Reply-To: <49806110.6010502@carallon.com>

At Wed, 28 Jan 2009 13:43:44 +0000,
Will Wagner wrote:
> 
> Hi All,
> 
> I have configured alsa-lib 1.0.19 to remove the components I do not want for my embedded
> arm target. I do this with the configure options:
> 
> 	--disable-docs \
> 	--disable-aload \
> 	--disable-rawmidi \
> 	--disable-hwdep \
> 	--disable-seq \
> 	--disable-alisp \
> 	--disable-old-symbols \
> 	--disable-python \
>   	--with-alsa-devdir=/dev \
> 	--with-pcm-plugins="copy linear adpcm rate plug dmix softvol" \
> 	--with-ctl-plugins="" \
> 	--with-versioned="no" \
> 
> This builds a much reduced in size alsa-lib
> 
> However when I then try to build alsa-utils this fails because amidi and seq will not
> compile with the reduced alsa-lib
> 
> It seems to be there should be configure options in alsa-utils to disable more of its
> components than just alsamixer and alsatest.
> 
> I have worked around this by just removing amidi and seq from the SUBDIRS variable in
> Makefile.in but perhaps there is a better way of doing this?

Fixed no on GIT tree.  The configure script checks the availability of
each component now.


Takashi

      reply	other threads:[~2009-01-29 14:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28 13:43 alsa-utils compile issues Will Wagner
2009-01-29 14:45 ` 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=s5hab9atbkq.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=will_wagner@carallon.com \
    /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