-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please make a release, because 0.3.0 isn't compatible with fluidsynth 2.x #2
Comments
FYI On FreeBSD fluidsynth is unbundled. Please also unbundle fluidsynth, because it's best to use the package-installed version. |
Please do NOT use system-wide fluidsynth nor dynamically link. Plugins must be self-contained. The plugin does include a dedicated, patched, version of fluidsynth with hidden symbols, so that the plugin won't interfere with any other plugins that may also use fluidsynth. e.g. fluidsynth has a global shared cache. That is fine for applications but it is not suitable for use by different plugins that may not know about each other when loaded into the same host. |
Ok, thanks. |
PS. a longer explanation of the issue is http://lists.ardour.org/pipermail/ardour-users-ardour.org/2018-November/028948.html |
Thank you, Robin, I changed it back to bundled in the FreeBSD port. |
I'll make a release regardless sometime soon (to include the fluidsynt 2.0.2 update) |
See https://ptpb.pw/yOuk
The text was updated successfully, but these errors were encountered: