RT: eassynth backend should not include all the sonivox library sources

[pedrolcl]

This comes from SourceForge Ticket 44.

Currently, the eassynth RT backend includes the sonivox library sources, which are compiled and statically linked. Instead, the build system should search for an external sonivox library like any other dependency, and dynamically link the shared library when found. The RT backends are currently used by these applications:

• drumstick-vpiano (from the drumstick utils)
• VMPK
• dmidiplayer

The sonivox library is not yet released, but I'm working on it. It is only a few days away. is already released. Please find here the source tarballs.

There are two other projects/prototypes that use this library in my portfolio. They embed it as a git submodule, or find it as an external dependency:

• Linux-SonivoxEAS
• multiplatform-sonivoxeas

I prefer to have all the code in a single place, avoiding duplication. But it is not only my personal convenience, Linux users would have a single copy of the library installed in their systems, which will be easier to patch or replace by the distribution vendors when needed. Of course this would be not possible if their only choice is to install the applications as an AppImage, or a Flatpak.

This is currently pending on implementation.

[dvzrv]

The sonivox library is not yet released, but I'm working on it. It is only a few days away.

As long as it is released and buildable before drumstick's next release, I have no issue with adding that as a new dependency!

[pedrolcl]

David, are you already maintaining 885 Arch packages? really? Maybe I'm wrong, but if not then I understand that one more doesn't really matter.

[pedrolcl]

There is another discussion thread about the release of the sonivox library.

[pedrolcl]

Drumstick v2.7.0 has been released.