@didipiman Sounds good.
One thing you can do is use otool to inspect the paths for a pre-existing external library that has a dependency. Try
- Make sure
fluid~will instantiate properly on a canvas.
- Find the
fluid~lib in your Purr Data app bundle. Use
otool -Lto inspect its dependencies. It should have a dependency on a fluidsynth library which I ship with Purr Data.
- Go to the directory in the app bundle where that fluidsynth lib lives.
- Use otool to figure out its install name
Once you get that info, put your libusb dylib library in the exact same directory inside the app bundle as the fluidsynth library. Then use install_name_tool/otool to set the same path relationship helios and libusb binaries that you saw with fluid~ and fluidsynth
I'll try to do the same the next time I get access to a mac machine.