Am 30. Dezember 2023 17:38:18 MEZ schrieb Alexandre Torres Porres porres@gmail.com:
/Users/porres/Documents/Pd/externals/ssr/ssr_vbap~.pd_darwin:dlopen(/Users/porres/Documents/Pd/externals/ssr/ssr_vbap~.pd_darwin, 10): Library not loaded: @loader_path/libfftw3f.3.dylib Referenced from: /Users/porres/Documents/Pd/externals/ssr/ssr_vbap~.pd_darwin Reason: no suitable image found. Did find: /Users/porres/Documents/Pd/externals/ssr/libfftw3f.3.dylib: cannot load 'libfftw3f.3.dylib' (load command 0x80000034 is unknown)
Which basically means, that the libfftw3f.3.dylib shipped with the SSR externals was built for a newer version of macOS.
https://stackoverflow.com/questions/77380844
many workflows (including mine) use brew to provide build- and runtime-dependencies. Unfortunately, brew (like Apple) only support the last three macOS releases. It's not so trivial to get bottled binaries of your dependencies with am extended life cycle (so you do not have to rebuild the world in your ci/cd system).
Personally (in my projects, so unrelated to SSR), I'm more and more inclined to just tell people that if they want to stick with their shiny apples, they need to play by apple's rules. Luckily, I'm not entirely convinced yet (but it's increasingly hard to reason why unpaid freelance volunteers should invest time and money to keep things from breaking, where those who get the big money are not concerned at all)
mfg.sfg.jfd IOhannes