putting shared libs *inside* your application

Post: #1
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.

Any ideas?
Quote this message in a reply
Posts: 3,591
Joined: 2003.06
Post: #2
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.
Quote this message in a reply
Posts: 869
Joined: 2003.01
Post: #3
You must add a copy files phase to your xcode target, set it to "Framework", and place the framework/libs in it.
Quote this message in a reply
Posts: 86
Joined: 2005.01
Post: #4
Yeah, you can just use XCode to package the Framework inside the .app package.
Quote this message in a reply
Post Reply 

Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  ios/mac shader - shared glsl source OptimisticMonkey 2 7,362 Jun 17, 2011 08:59 AM
Last Post: OptimisticMonkey
  shared context breaking FTGL texture fonts akb825 12 10,504 Sep 7, 2006 08:56 PM
Last Post: akb825
  g++ `sdl-config --libs --cflags` in xcode freemanen 4 5,628 Aug 28, 2005 04:06 AM
Last Post: freemanen
  SDL shared library error? Red Marble Games 0 2,661 Jul 8, 2005 12:51 PM
Last Post: Red Marble Games
  shared context bug?? NYGhost 5 4,845 Mar 8, 2005 01:22 PM
Last Post: NYGhost