Comments on: How To use Dynamic Libraries in Xcode 3.1 (using FMOD)

By: Martin Robinson

Martin Robinson — Sat, 27 Feb 2010 16:04:14 +0000

Just trying to do this where more than one FMOD lib is used... you also need to change the library paths for the additional library linking to libfmodex.dylib. I'm using libfmodevent.dylib for example and the script then needs to be something more like below (BTW I've defined FMOD_SDK as a source tree in Xcode which is what that refers to):


mkdir "$TARGET_BUILD_DIR/$PRODUCT_NAME.app/Contents/Frameworks"
cp -f $FMOD_SDK/fmod/api/lib/libfmodex.dylib "$TARGET_BUILD_DIR/$PRODUCT_NAME.app/Contents/Frameworks/libfmodex.dylib"
cp -f $FMOD_SDK/fmod/fmoddesignerapi/api/lib/libfmodevent.dylib "$TARGET_BUILD_DIR/$PRODUCT_NAME.app/Contents/Frameworks/libfmodevent.dylib"
install_name_tool -change ./libfmodex.dylib @loader_path/../Frameworks/libfmodex.dylib "$TARGET_BUILD_DIR/$PRODUCT_NAME.app/Contents/MacOS/$PRODUCT_NAME"
install_name_tool -change ./libfmodex.dylib @loader_path/../Frameworks/libfmodex.dylib "$TARGET_BUILD_DIR/$PRODUCT_NAME.app/Contents/Frameworks/libfmodevent.dylib"
install_name_tool -change ./libfmodevent.dylib @loader_path/../Frameworks/libfmodevent.dylib "$TARGET_BUILD_DIR/$PRODUCT_NAME.app/Contents/MacOS/$PRODUCT_NAME"

By: – Compile and Use Boost Libraries in Xcode & Visual Studio BrockWoolf.com

Sun, 20 Sep 2009 04:52:45 +0000

[...] The actual process of scripting the dylib copy and modifying the darwin executable are already covered in another article I wrote here: How To use Dynamic Libraries in Xcode 3.1 [...]

By: Jeremy

Jeremy — Thu, 03 Sep 2009 15:23:23 +0000

@Steve

The FMOD package comes with example iPhone XCode projects which show how to set them up without the need of directly importing the dylib or making a run script. Check out the header search path and the xcconfig files.

By: FengShuiAvenger

FengShuiAvenger — Sat, 29 Aug 2009 10:44:25 +0000

After desperately searching Apple's Mac OS X reference library, and trying numerous google searches, this article came up. Thanks for posting this, I can finally stop screaming at my monitor.

By: Brock

Brock — Tue, 28 Jul 2009 11:28:25 +0000

No worries guys! Just glad to help out other Mac users

By: Ojaswa

Ojaswa — Tue, 28 Jul 2009 10:50:18 +0000

Thanks Brock!

Very helpful article indeed. you saved my time

By: Ash

Ash — Mon, 18 May 2009 08:29:06 +0000

Thank you very much for the article.. its superb..

By: Brock

Brock — Fri, 15 May 2009 18:30:09 +0000

@Sean

Hey Sean, sorry for my late reply I have been immensely busy. Yes there are limitations to this technique, I have been told me someone one the interwebs that there is a better way to do this linking (although I have not actually been shown what it is). The advantage that this technique brings is that although it is a pain, it is a one click build solution which is what we should aim for in our development.

I am familiar with putting the libraries in the user's local library directory. I do however think this is an inferior approach because it means you have to touch a part of the system that requires admin privileges. What if another developer did the same thing with a different version of the framework? It's possible you could break another application if the frameworks are named identically. Also your uninstaller tool needs to remember to remove this directory when the user uninstalls your application. Otherwise it will take up space forever. The user will never even know it was installed there.

Those are the main reasons why I believe the framework should be bundled with the application. It binds with the Apple guidelines of a simplified "Drag and drop" install. And anyways, frameworks are usually pretty small these days.

Cheers,
Brock

By: Sean

Sean — Wed, 11 Mar 2009 20:07:05 +0000

Hi! Great info. I was trying to use this advice with Boost and I found out that there are some limitations to this technique (at least for command line tools). For one thing, if the app is run as a script, the working directory will not (necessarily) be that of the executable, and the library will not be found.

Another option is to put dynamic libraries where they can be found e.g. /usr/local/lib. Then you can skip the copy step and just drag the libs. Of course, you would have to take this into account when deploying, but it works great for development!

If interested, I describe the steps in detail

- Sean

By: satyanarayana

satyanarayana — Thu, 26 Feb 2009 10:57:04 +0000

Hi,

Thanks a lot for this article. It is really good. Could you please add the following description.
If it is user defined dynamic library then user has to set "install name" property to ./dynamic library name (like ./libxyz.dylib).