All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Wagner <will_wagner@carallon.com>
To: alsa-devel@alsa-project.org
Subject: alsa-utils compile issues
Date: Wed, 28 Jan 2009 13:43:44 +0000	[thread overview]
Message-ID: <49806110.6010502@carallon.com> (raw)

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?

Thanks,

Will


-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner@carallon.com
Development Manager                      Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------

             reply	other threads:[~2009-01-28 13:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28 13:43 Will Wagner [this message]
2009-01-29 14:45 ` alsa-utils compile issues Takashi Iwai

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=49806110.6010502@carallon.com \
    --to=will_wagner@carallon.com \
    --cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.