[CLAM] Problems using jackdmp instead of jackd on OSX

[Pau Arumi]

Hi Stéphane,
it's nice to see you by the clam list again :-)

>
> It seems to work, but what would be the good what to package CLAM then?
>
That's a good question. We'd like to not require the users have jack 
installed
(in osx at least), so that's why we bundle libjack.dylib together with 
the app
(the lib functions can see if the jackd is running or not, and try to 
start it).

If I understand well, the problem with that approach is that we cannot 
choose
a different jack implementation (jackdmp) or even a different jackd version
(from the library version).

AFAIK, other jack-aware apps,  Ardour and Hydrogen for instance, does 
(statically)
link with libjack. So they have the same problem, or worst because you 
cannot "link"
libjack.dylib to libjackdmp.dylib for instance.

I've been also looked into the jackosx since you are one of the authors, 
to see if jackpilot
could handle both jackd and jackdmp but it does not. (i can start 
jackdmp  by
commandline) but jackpilot refuses to open.

So can you think in any flexible solution on mac osx allowing to choose 
the two jack
implementations? (not requiring jack system-wide installation is a plus)
Maybe only use jack through the JAR (jack-audio-router coreaudio driver)?

Pau