libjack object files included in libjack and libjackserver about jack1 HOT 5 CLOSED

There seems to be some confusion here.

libjack and libjackserver should never be linked against by the same process. libjackserver is specifically intended as a special version of libjack for use by the server (and also by programs that can actually become the server).

I have reviewed the drivers, and they all use libjackserver only. jackd also ONLY links against libjackserver.

Where and/or why do you believe that a process is being linked against both libraries?

from jack1.

Wow, I thought this had gravestoned.

I'll have to scour a little back through that and the code to see what I
was getting at.

Off the top of my head it wasn't so much about what was being linked as the
fact that symbols were present in multiple places, and for some reason I
was seeing C++ things destroyed when they shouldn't be.

Give me a few months .-)

D

On Fri, Jul 3, 2015 at 6:03 PM, Paul Davis [email protected] wrote:

There seems to be some confusion here.

libjack and libjackserver should never be linked against by the same
process. libjackserver is specifically intended as a special version of
libjack for use by the server (and also by programs that can actually
become the server).

I have reviewed the drivers, and they all use libjackserver only. jackd
also ONLY links against libjackserver.

Where and/or why do you believe that a process is being linked against
both libraries?

—
Reply to this email directly or view it on GitHub
#12 (comment).

from jack1.

They should be in multiple places, but those places should never come together in a single process. That's the idea, at least.

from jack1.

Evening Paul,

They should be in multiple places

What is the rational for this? Surely shared libraries are a great thing to
use? The suggested resolution patch was about linking libjackserver.so
against libjack.so and having jackd use both. The motivation was from
skipping some lifecycle issues arising from the duplicated symbols - C++
static lifecycle was how I originally noticed it (IIRC, it's been a while).

Are there perhaps cache coherency issues or having the code in a single
blob dictating this?

The reason I ask is that if there's something I'm missing (eminently
probable) I'll skip on the deeper investigation .-)

D

from jack1.

Your thinking too hard. libjackserver exists to build JACK servers and their backends. libjack exists to build clients. They are not intended to both be used by a single process. libjackserver contains some special extra magic compared to libjack that allows a process linked against it to become a server (even if it is not jackd), and this extra magic requires the use of a different library.

You should probably take the suggestion to jack-devel, where Stephane Letz (who originated the libjackserver idea) might comment on it.

from jack1.