You need to put the dylibs *inside* the bundle, into the same folder as the actual binary, which is SoundFileManager.debug.app/Contents/MacOS/ in your case.
On OS X, a .app is really a folder, not the app itself. Inside that folder you can store resources (like images, config, dylib).
If you right-click (or ctrl-click if you have one button mouse) on the .app, you will see something like "Show Contents" in the popup menu.
That should open up a new finder window, where you can browse to the MacOS folder and copy the dylibs into there.
The ones that come with the module have been modified slightly in order to run from inside a bundle. Originally they are set to run from the same folder as a non-bundled app (ie. non-gui app), but that's not much use for us BlitzMax users.
If BlitzMax builds had post-processing then you could automate the copying of the dylibs into the folder.
But once you've copied them in there, they should be there after successive builds.
HTH
Brucey
On OS X, a .app is really a folder, not the app itself. Inside that folder you can store resources (like images, config, dylib).
If you right-click (or ctrl-click if you have one button mouse) on the .app, you will see something like "Show Contents" in the popup menu.
That should open up a new finder window, where you can browse to the MacOS folder and copy the dylibs into there.
The ones that come with the module have been modified slightly in order to run from inside a bundle. Originally they are set to run from the same folder as a non-bundled app (ie. non-gui app), but that's not much use for us BlitzMax users.
If BlitzMax builds had post-processing then you could automate the copying of the dylibs into the folder.
But once you've copied them in there, they should be there after successive builds.
HTH
Brucey