Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.co.uk>
To: Jaroslav Kysela <perex@suse.cz>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: alsa-lib bloat.
Date: Sat, 09 Dec 2006 11:09:18 +0000	[thread overview]
Message-ID: <457A995E.6080708@superbug.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.61.0612090908570.13335@tm8103.perex-int.cz>

Jaroslav Kysela wrote:
> On Fri, 8 Dec 2006, James Courtier-Dutton wrote:
> 
>> Hi,
>>
>> On my desktop system, I have this:
>> /usr/lib/libasound.so.2.0.0
>> size: 2785380 bytes.
> 
> Have you tried to build minimal alsa library?
> 
>   --disable-aload         disable reading /dev/aload*
>   --disable-mixer     Disable the mixer component
>   --disable-pcm       Disable the PCM component
>   --disable-rawmidi   Disable the raw MIDI component
>   --disable-hwdep     Disable the hwdep component
>   --disable-seq       Disable the sequencer component
>   --disable-instr     Disable the instrument component
>   --disable-alisp     Disable the alisp component
> 
>   --with-pcm-plugins=<list>  Build PCM plugins
> 
> Note that only hw plugin is important for pcm if applications will do all 
> conversions itself.
> 
> Just quick test with:
> 
> ./configure --disable-aload --disable-mixer --disable-rawmidi 
> --disable-hwdep --disable-seq --disable-instr --disable-alisp 
> --with-pcm-plugins=hw
> 
> strip -g --remove-section=.comment --remove-section=.note libasound.so
> 
> -rwxr-xr-x  1 perex users 366562 2006-12-09 09:22 libasound.so.2.0.0
> 
> It does not look so bad, doesn't?
> 
> With mixer stuff:
> 
> -rwxr-xr-x   1 perex users 420024 2006-12-09 09:25 libasound.so.2.0.0
> 
>> 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.
> 
> The best thing is to discuss what else can be shrinked (removed from 
> build). If embedded platform developers stay quiet, we won't care.
> 
> For example, all dynamic configuration code can be removed, too.
> 
> 						Jaroslav
> 

Thanks, that is a good start. I have entered that information into the 
alsa wiki.

https://bugtrack.alsa-project.org/wiki/wikka.php?wakka=AlsaEmbedded



-------------------------------------------------------------------------
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

  reply	other threads:[~2006-12-09 11:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08 12:37 alsa-lib bloat James Courtier-Dutton
2006-12-09  8:25 ` Jaroslav Kysela
2006-12-09 11:09   ` James Courtier-Dutton [this message]
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=457A995E.6080708@superbug.co.uk \
    --to=james@superbug.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=perex@suse.cz \
    /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