If you don't change the Installation Directory build setting, I think "/usr/local/lib" is the default value. That is then written to the lib when it's linked. I change mine to ".", but my target isn't a bundle. The "Installation Directory" setting did not seem to make a difference in my case and from what I have since read, it seems the bundle_loader flag would be what I need to correctly resolve the externals from the executable that loads the bundle. However it does not appear that this could be directed at a dylib. I think I may look at a design change here to avoid the plugins, particularly as I am not keen on also having to solve this on Windows and Linux. :-) Thanks again though.
If you don't change the Installation Directory build setting, I think "/usr/local/lib" is the default value. That is then written to the lib when it's linked. I change mine to ".", but my target isn't a bundle.