Xcode, building and dylibs

I've looked at a few related questions and cannot seem to find a solution for myself.

Basically I'm using the libmp3lame.dylib in my Xcode project. The install process for lame produced the .dylib and placed it in usr/local/lib and to get Xcode to build and run the project I changed the Library Search Paths to include the above folder. This works fine.

Now it's come to producing a release version and I want to include the .dylib in the bundle so that the user doesn't have to put up with an in开发者_开发知识库stall phase or anything similar. I created a copy files phase of the target and this dumps the .dylib into the Frameworks folder in the contents of the bundle. However, running otool on the binary shows that instead of using the .dylib inside the bundle, the compiler has linked it to the usr/local/lib version (even if I delete that version).

Looking at the other results in the otool output I have other frameworks being linked to inside the bundle, just not the .dylib. Looking at the properties for both these frameworks and the .dylib in Xcode I can't see any differences other than file type.

My searching suggests I need to use rpath or similar, but I've no clue where to apply this in Xcode.

My workaround for this issue was to do the following in terminal (I've used Automator to, well, automate this):

install_name_tool -id @executable_path/../Frameworks/libmp3lame.0.0.0.dylib ~/path/to/lib/in/app/libmp3lame.0.0.0.dylib

install_name_tool -change /usr/local/lib/libmp3lame.0.dylib @executable_path/../Frameworks/libmp3lame.0.0.0.dylib ~/path/to/app/Contents/MacOS/AppName

Basically swapping the path to the library from the one in the usr local lib to the one included in the bundle.

My tip is to look at the build output, how does it actually run ld?