At Wed, 28 Mar 2007 19:11:17 +0200, I wrote: > > At Wed, 28 Mar 2007 10:06:01 -0700, > John Utz wrote: > > > > > > -----Original Message----- > > From: Takashi Iwai [mailto:tiwai@xxxxxxx] > > Sent: Wed 3/28/2007 3:13 AM > > To: John Utz > > Cc: alsa-devel@xxxxxxxxxxxxxxxx > > Subject: Re: is statically linking libasound supported? because if i do > > it, i cant open the device! > > > > At Tue, 27 Mar 2007 18:05:50 -0700, > > John Utz wrote: > > > > > > but it fails to find hw:0,1 if i link it statically, is that expected behavior? > > > > Did you check alsa-lib/INSTALL file? > > For creating a static lib, you have to use --disable-shared _and_ > > --enable-static. > > > > Why would i need to --disable-shared? i wanted both! > > You cannot build both *.a and *.so _at the same time_ for alsa-lib. > partly because of bad behavior of libtool, partly because of the > design of alsa-lib (embedded plugins in static lib). > > Simply build twice, once for a shared lib and once for a static lib. > > > > I got the libasound.a just find and it linked the app and the app *runs*, it just > > doesnt find the device! > > The libasound.a is broken. Well, I meant the libasound.a you made is broken. When you build libasound.a without --disable-shared, it passes -DPIC and it's built with assumption of shared library use. Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
