Re: [Jack-Devel] major change in jack1 MIDI handling

PrevNext  Index
DateSat, 12 Oct 2013 14:54:06 -0400
From Paul Davis <[hidden] at linuxaudiosystems dot com>
ToChristian Schoenebeck <[hidden] at crudebyte dot com>
CcJACK <[hidden] at lists dot jackaudio dot org>
In-Reply-ToChristian Schoenebeck Re: [Jack-Devel] major change in jack1 MIDI handling
Follow-UpChristian Schoenebeck Re: [Jack-Devel] major change in jack1 MIDI handling
On Sat, Oct 12, 2013 at 2:48 PM, Christian Schoenebeck <
[hidden]> wrote:

>
> And with distros it's a nightmare. Some distros use JACK1, some JACK2, some
> ship both, but then they are not optimally packaged, which regularly
> causes a
> newly compiled app to crash, because it compiled and linked against JACKx,
> while accessing server JACKy at runtime, which sometimes is hard to
> resolve.
> And if you want to switch from one JACK to the other, you might need to
> recompile half of your system.
>

This is completely FALSE.

Jack1 and Jack2 remain API and ABI compatible unless an app has used
features of one that are not present in the other (which is rare).

I have routinely switched between Jack1 and Jack2 without recompiling any
of my JACK clients. I have interacted with many individuals on IRC who have
done the same, sometimes many times in one day.

If it doesn't work on distro X, then that is because distro X has
mispackaged things, and not in a JACK-specific way, but in way that relates
to a generic mistake with linking.

--p
PrevNext  Index

1381604055.9192_0.ltw:2, <CAFa_cK=wy0zwJbgZkjCDF7vab6=YT2t7eORsyRS+ej_ptciqug at mail dot gmail dot com>