On Tue, 2022-05-03 at 14:35 -0300, Alexandre Torres Porres wrote:
Em ter., 3 de mai. de 2022 às 12:40, Roman Haefeli reduzent@gmail.com escreveu:
I guess I'll have to join the fluidsynth list and ask for that. Maybe they can also help me with the other issue where even a x86_64 fluidsynth installed for monterey via homebrew doesn't work in earlier versions of macOS.
I'm not sure this would be the right place to ask. What they provide, works. The issues that the homebrew team is trying to address with their way to do things are probably not related to the source code, but more related to how things work on new Macs.
but they provide pre built stuff at https://github.com/FluidSynth/fluidsynth/releases/tag/v2.2.7
and I already did ask for universal builds and there was some interest where someone said "I'm open to publish those universal binaries with the fluidsynth releases. I could sign them as well" see https://lists.nongnu.org/archive/html/fluid-dev/2022-05/msg00002.html
Well, glad you already asked, then!
I often find things are a bit easier on Linux, but that's what I got accustomed to. In the case of the fluidsynth~ external, using the dynamic libraries from my distro (Ubuntu 22.04) doesn't seem practical, as libfluidsynth.so.3 links against virtually half the system. After executing the localdep script, I end up with 53 *.so files. Most of them aren't actually used when libfluidsynth is used for the pd external. Creating a more stripped down build of libfluidsynth probably would make sense here.
Cool, but how? :)
By building fluidsynth from source with the minimal set of configure flags required for the pd external.
Roman