but don't understand how this is done on Linux.
As I've written in the original thread:
Linux: -Wl,-rpath,"$$ORIGIN",--enable-new-dtags
This makes sure that the loader will look for dynamic libraries in the same folder as the Pd external. This is what pd-lib-builder uses for shared helper libraries, but it works for any shared library.
Christof
On 07.01.2021 15:20, Roman Haefeli wrote:
On Thu, 2021-01-07 at 07:40 -0300, Lucas Cordiviola wrote:
here:
https://nc.nubegris.com.ar/index.php/s/nRWQi3CBCdYctHx https://nc.nubegris.com.ar/index.php/s/nRWQi3CBCdYctHx
are linux64/32 test versions that includes fluidsynth 2.1.6
feedback is welcomed
Works for me. Your libfluidsynth dynamic library is very stripped down. I checked the one from repos of Ubuntu 20.04 and it links to a lot of other libraries (jack, opus, systemd, wayland etc.) that probably don't make any sense in the given use case. How did you create yours? Did you just compile yourself with everything disabled? How do you link fluid~ to the local libfluidsynth.so? I followed the thread about including local libraries on macOS on Windows, but don't understand how this is done on Linux.
Roman
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list