From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: pcm_jack and jack chicken-and-egg situation Date: Wed, 05 Mar 2003 10:49:02 +0100 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <1046822550.8620.193.camel@insanity.tek.net> <20030305101157.3373dbfc.mdeboer@iua.upf.es> Mime-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <20030305101157.3373dbfc.mdeboer@iua.upf.es> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Maarten de Boer Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Wed, 5 Mar 2003 10:11:57 +0100, Maarten de Boer wrote: > > Bob Ham wrote: > > The new pcm_jack thing presents a bit of a chicken and egg problem; I > > just compiled alsa-lib twice because jack depends on alsa-lib and if you > > configure alsa-lib with jack support, it depends on jack. Would it be > > possible for pcm_jack to be distributed seperately? > > Hi Bob, > > That's indeed a problem I did not realize... And there is an another, > related problem, which is that with binary distributions, you have > to either distribute to versions, one linked against jack and one not > linked against jack. > > The ALSA plugin's are all compiled into the library. It would indeed be > nice if each plugin would be a seperate shared object. you can specify the so file and the function name via pcm_type definition: pcm_type.foo { comment foo type plugin lib /usr/lib/libfoo.so open my_foo_open } Takashi ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf