On Jan 28, 2011, at 11:56 AM, Abhijeet Singh wrote: > I was wondering whether it would be a good idea to keep all these libraries > inside the application bundle itself?
That would be much better, and is the recommended practice on the Mac. > Similarly there are number of input files that my application uses. At > present these files are kept in "Library/Application Support/MyApp" folder. > These files also be kept inside the bundle. That depends on what kind of files they are. If these files could be changed in the normal course of using your app, you can't put them in your application's bundle (however, you could put templates for these files in your bundle and install the ones to be edited in Application Support). Otherwise, placing them in your resources folder is generally a good idea. > What could be the major disadvantages of this approach? For the user, there are none. OTOH, depending on how your libraries are built, keep in mind that the user can run a .app from anywhere, so if your libraries expect to be at some absolute path, that will break. Many Unix open source libraries need to be slightly adapted, and you may have to use @loader_path or the likes when building your libraries for everything to work and for the linker to find everything at startup. Cheers, -- Uli Kusterer "The Witnesses of TeachText are everywhere..." _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
