yeah, I'm desperately trying to warn how I don't really speak the language. All I did before was read that script and try to find how you were using name_tool and the other things, and it all just failed. I wasn't aware I could just run the script. And it took me a while to get there even now. I almost needed you to tell me all the steps in detail:

"1- get that script file and put it in the folder you built your external
2- open terminal at that folder run the script by typing "./localdeps.macos.sh external.extension"

 

They sure did a lot of magical stuff and made many dylib appear inside the folder. So I zipped it and tested it in another machine that doesn't have fludsynth installed, and it worked! But I'm not convinced I need ALL the dylib files that poped out.

They are:

libvorbisenc.2.dylib 

I thought I only need libfluidsynth.2.dylib but now if I delete the rest and try to open the external, I do get those errors of missing links. So yeah, maybe I need these all, but I'm not so sure. I checked Purr Data's libs and at least I didn't see 2 of these: libopus.0.dylib & libreadline.8.dylib. Not that it makes that much of a difference just getting rid of these two out of so many.

Anyway, Lucarda said he was having success building for Windows, but I'm not so sure now. Well, my mac build can be found here: https://github.com/porres/pd-fluidsynth/releases/tag/test-1

So others who don't have fluid~ or fluidsynth installed can also try it :) 

Well, thanks again for this

cheers