Re: [VMPK-devel] Distributing VMPK binaries
Virtual MIDI controller for Linux, Windows and OSX
Brought to you by:
plcl
From: Pedro Lopez-C. <ped...@gm...> - 2012-06-07 11:44:39
|
Hi All, On Thu, Jun 7, 2012 at 10:54 AM, Robin Lee <rob...@gm...> wrote: > Hi, I saw r329 heavily patched RtMidi. Will the changes be merged RtMidi > upstream? In Fedora, we built a shared RtMidi. So I hope VMPK will always > compile with the vanilla RtMidi. > > cheers, > robin > I repeat here my comment to the Sourceforge bug #3532659: The upstream tarball of RtMIDI 1.0.15 does not support compilation as a shared library out of the box. Its author has always expected to include the three source files into another projects, and that is what VMPK always did. Upstream never warranted source or binary compatibility. If Fedora and Debian boldly went ahead and took the decision of packaging RtMIDI as a dynamic library without asking the interested parties, and without letting know all upstream authors about this decision, then it is the burden of Fedora and Debian who needs to take care of the consequences, and patch every program that is not aligned with their release schedules, and take care of the appropriate SOVERSION changes when there are incompatible changes in the library. Now, about our changes over RtMIDI 1.0.15 in VMPK's SVN repository: I don't know if this is going to be merged into upstream RtMIDI some day. We have sent the patch to Gary already. In the past I've patched RtMIDI to fix bugs and include new functionality. When I did that, I've always included first the changes in VMPK, and sent the patches to Gary who included them in later versions. Sometimes much later. Next VMPK release will include a very interesting feature, enabling the users to change the MIDI backend at runtime, between several backends (like ALSA and Jack) compiled together into the same executable. A fine job made by Gilles Filippini. Thanks! As a note aside: the VMPK package distributed by Fedora and Debian is useless for most people, because its poor integration. Many programs (like Timidity) in Fedora and Debian don't work with Jack MIDI, because they only have ALSA sequencer support. Jack MIDI is only useful for user of Ardour and so-called "professional audio software", who have very little use for VMPK. OTOH, VMPK is intended for hobbyist, students, and as a children's game: an audience that probably never needs or wants Jack MIDI. Regards, Pedro > On Tue, Mar 13, 2012 at 2:01 PM, Pedro Lopez-Cabanillas < > ped...@gm...> wrote: > >> Hi, >> >> I think that a correct way to handle the different backends in VMPK 0.4.0 >> is >> this: >> >> http://aur.archlinux.org/packages/vm/vmpk/PKGBUILD >> >> AUR builds the three backends, creating three different binaries with >> different names, which can coexist installed on the same system. I think >> that >> Debian and Fedora could do something similar, offering three different >> binary >> packages created from the same sources, or packaging all variants together >> like Debian does for the fftw3 library. >> >> Regards, >> Pedro >> > > |