From: James Courtier-Dutton <James@superbug.co.uk>
To: alsa-devel@lists.sourceforge.net
Subject: alsa-lib bloat.
Date: Fri, 08 Dec 2006 12:37:01 +0000 [thread overview]
Message-ID: <45795C6D.9030100@superbug.co.uk> (raw)
Hi,
On my desktop system, I have this:
/usr/lib/libasound.so.2.0.0
size: 2785380 bytes.
libasound is really too big for what is does.
I was talking to some embedded platform developers recently, and they
really don't like it at all.
Could something be done about it?
I was thinking that we could really cut down the API to a very limited
subset of the current api, and place #ifdef in the source code, so that
developers could build alsa-lib for embedded systems using just this
subset of the current api. I would suggest just using the poll()
callback method would be needed, as then it is similar to Mac OS X, and
generally accepted as the best way to talk to a sound device.
I would also like to ask any embedded developers out there who have
already done this, to post patches back to ALSA so that it saves
developers time in future.
How about also separating libasound into separate libs, one for PCM, one
for MIDI, and one for CONTROL that could in turn use a separate "helper
functions" lib for any common functions. Some embedded applications
might not need any of the MIDI/sequencer stuff.
Any comments?
James
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next reply other threads:[~2006-12-08 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 12:37 James Courtier-Dutton [this message]
2006-12-09 8:25 ` alsa-lib bloat Jaroslav Kysela
2006-12-09 11:09 ` James Courtier-Dutton
2006-12-09 14:38 ` Liam Girdwood
2006-12-19 10:03 ` Takashi Iwai
2006-12-13 19:31 ` Steve deRosier
2006-12-14 9:01 ` Clemens Ladisch
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=45795C6D.9030100@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
/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.