Skip to contentSkip to conversation

pcm_jack and jack chicken-and-egg situation

DISCUSSION Bob Ham 3 participants 4 messages Mar 5, 2003

lore
Share & tools
lore

Bob Ham

author
#0 lore raw

Hi all,

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?

Cheers,

Bob

Signature · 9 lines
Bob Ham <[email protected]>



-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com
#1 lore raw

At 05 Mar 2003 00:02:30 +0000,

Quoted 6 lines · Bob Ham

Hi all,

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.

yep.

Quoted 2 lines

Would it be
possible for pcm_jack to be distributed seperately?

or it wouldn't be bad to have an alsa-lib-plugin SDK. we don't have to implement all plugin objs in libasound.so.

Takashi

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

#2 lore raw
In reply to Bob Ham
Quoted 4 lines · Bob Ham

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. Maybe Jaroslav has concrete objections against this? Anyway, it would represent quite a bit of change to the code, which I suppose just before 0.9.0 final is not the best moment..

Another solution would be not to link against jack, but use the dynamic linker loader (dlopen, dlsym). This would require to link against libdl, but I suppose that that is okay.

Maarten

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

#3 lore raw

At Wed, 5 Mar 2003 10:11:57 +0100,

Quoted 9 lines · Maarten de Boer
Quoted 4 lines · Bob Ham

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,

Quoted 7 lines

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