From: Ciaccia <ciacciax@yahoo.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Static build of alsa-lib
Date: Fri, 16 Mar 2007 08:11:20 -0700 (PDT) [thread overview]
Message-ID: <393830.60990.qm@web31012.mail.mud.yahoo.com> (raw)
In-Reply-To: <s5hzm6duuzw.wl%tiwai@suse.de>
Hi Takashi,
Thanks for the answer. To I need both the patches or
just the first one? Which alsa-lib release should I
use with the patch, 1.0.13?
PS: sorry, what is the HG tree?
--- Takashi Iwai <tiwai@suse.de> wrote:
> At Fri, 16 Mar 2007 15:18:04 +0100,
> I wrote:
> >
> > At Fri, 16 Mar 2007 06:17:00 -0700 (PDT),
> > Ciaccia wrote:
> > >
> > > Hi there,
> > > I would like to compile an alsa application for
> an
> > > embedded system with no shared-libraries
> support. My
> > > application just needs PCM, with no plug-ins, no
> mixer
> > > and no midi and the application should be a
> standalone
> > > executable with no external dependencies,
> otherwise it
> > > will not work.
> > >
> > > I tried to compile alsa-lib with static support,
> but
> > > without luck (-ldl is always needed in the gcc
> line
> > > and gcc always prints some weird warnings).
> Since I
> > > don't need external plugins nor ladspa, I think
> there
> > > should be a way to compile an application in a
> 100%
> > > static manner, but I still have to figure out
> how.
> > >
> > > I also found this thread with a similar problem
> with
> > > uClinux
> > >
>
http://www.mail-archive.com/alsa-user@lists.sourceforge.net/msg18253.html
> > > but at the end I did not understand how/if the
> problem
> > > was solved.
> > >
> > > Do you think it should be possible to compile
> alsa-lib
> > > with no dependencies on dl? How?
> > >
> > > Otherwise, would it be possible to write an alsa
> > > application that does not rely on alsa-lib
> (i.e.,
> > > by using the alsa kernel APIs directly)? Has
> someone
> > > already tried it? Some hints?
> > >
> > > Every hint is extremely welcome
> >
> > I worked on this sometime ago, and made a patch to
> build alsa-lib
> > without pthread and libdl. I don't remember why
> this wasn't applied.
> > IIRC, ulibc has the wrappers for pthread and
> libdl, so this wasn't
> > needed at that time in the end.
> >
> > Otherwise, it should work. Build with
> --enable-static
> > --disable-shared, --disble-mixer, --disable-hwdep,
> etc.
>
> ... oh, not perfectly if really no pcm plugin is
> used.
> The patch below fixes the build problem. Already
> applied to HG tree.
>
>
> Takashi
>
> diff -r f1203eb7eb48 configure.in
> --- a/configure.in Tue Mar 13 10:44:28 2007 +0100
> +++ b/configure.in Fri Mar 16 15:18:21 2007 +0100
> @@ -371,6 +371,7 @@ fi
>
> dnl Create PCM plugin symbol list for static
> library
> rm -f "$srcdir"/src/pcm/pcm_symbols_list.c
> +touch "$srcdir"/src/pcm/pcm_symbols_list.c
> for t in $PCM_PLUGIN_LIST; do
> if eval test \$build_pcm_$t = yes; then
> echo \&_snd_module_pcm_$t, >>
> "$srcdir"/src/pcm/pcm_symbols_list.c
>
____________________________________________________________________________________
Don't get soaked. Take a quick peek at the forecast
with the Yahoo! Search weather shortcut.
http://tools.search.yahoo.com/shortcuts/#loc_weather
-------------------------------------------------------------------------
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 prev parent reply other threads:[~2007-03-16 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 13:17 Static build of alsa-lib Ciaccia
2007-03-16 14:18 ` Takashi Iwai
2007-03-16 14:24 ` Takashi Iwai
2007-03-16 15:11 ` Ciaccia [this message]
2007-03-16 15:20 ` Takashi Iwai
2007-03-17 10:13 ` Ciaccia
2007-03-20 10:48 ` Takashi Iwai
2007-03-20 12:00 ` Rene Herman
2007-03-20 15:13 ` Ciaccia
2007-03-20 16:01 ` [Alsa-devel] " Takashi Iwai
2007-03-21 19:00 ` Ciaccia
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=393830.60990.qm@web31012.mail.mud.yahoo.com \
--to=ciacciax@yahoo.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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