putting shared libs *inside* your application - Printable Version
+- iDevGames Forums (http://www.idevgames.com/forums)
+-- Forum: Development Zone (/forum-3.html)
+--- Forum: Graphics & Audio Programming (/forum-9.html)
+--- Thread: putting shared libs *inside* your application (/thread-5996.html)
putting shared libs *inside* your application - rzilibowitz - Jan 3, 2005 09:14 PM
I understand that a common practise is to place shared libraries a program links to inside the application bundle itself in mac os x. This is makes for much easier installs since users don't need to go and download and install SDL themselves fo example.
This is similar to just static linking in a sense but it manages to avoid the GPL issues with libraries like SDL.
Question: How do you configure an Xcode project to do this?? Has anybody else tried to do this. I'm sure there must be a simple and proper way of doing this, but not sure what it is yet.
putting shared libs *inside* your application - AnotherJake - Jan 3, 2005 09:35 PM
I'm not sure about all the issues involved with SDL but http://cocoadevcentral.com/articles/000042.php might be of interest to you. There has been some discussion here about this already. I wish I could remember where/what/when.
putting shared libs *inside* your application - DoG - Jan 4, 2005 04:31 PM
You must add a copy files phase to your xcode target, set it to "Framework", and place the framework/libs in it.
putting shared libs *inside* your application - ravuya - Jan 13, 2005 12:15 PM
Yeah, you can just use XCode to package the Framework inside the .app package.