Closed Eonfge closed 3 years ago
Is it 1.1.7 or the current head 2b291705f2043f39d219a49c2671c80f1dd422e0?
Ow, this is build against the latest release of ZMusic 1.1.3. This means you've already fixed the issue and we must just wait for the next release?
The latest release is 1.1.7. GitHub shows a wrong version because the newer tags have no assets attached to them. Support for dynamic loading of FluidSynth 2.2.x was added in 2b291705f2043f39d219a49c2671c80f1dd422e0 which isn't a part of any release yet.
I've been sleeping on the job :scream:
Well, consider this issue resolved. https://github.com/coelckers/ZMusic/commit/2b291705f2043f39d219a49c2671c80f1dd422e0 fixes the issue with the dynamic loading. For the time being, I'll downgrade to FS 2.1.8 so that I don't have to package any unofficial version.
You can configure ZMusic with DYN_FLUIDSYNTH=OFF
, and link to FluidSynth 2.2.x. Also, doing this prevents crashing when FluidSynth is built with libinstpatch. It's another issue fixed only in development version of ZMusic.
@alexey-lysiuk Those are some very useful titbits of information. Perhaps you should add a few of these things to a readme. Thanks anyway, as this allows me to fix some user-reported issues.
GZDoom 4.6.0 just has been released along with ZMusic 1.1.8. So, the mentioned information with quirks and workarounds is no longer relevant.
I'm on it. Hope to have an updated release in an hour or so. It's a shame though that Github can't notify me of new tags. That would make my live easier
Discovered when I tried to update the sound library for the Flatpak version
This is likely a simple issue, since the acutal cause seems to be an outdated
.so
reference. 2.2.0 only gives you the following headers and.so
files: