This is the preferred method of deployment. Experienced Mac users hate it when an installation scatters crud all over the filesystem. You should especially not be polluting /usr/local/lib.
Dave Carrigan Seattle, WA On Jan 28, 2011, at 2:56 AM, "Abhijeet Singh" <abhi_...@in.com> wrote: > Hi,I have number of static and dynamic libraries in my application. At > present i have kept all the libraries in "\usr\local\lib" folder. I was > wondering whether it would be a good idea to keep all these libraries inside > the application bundle itself? 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.The > advantage with this approach is I dont need to create different directories > on target machine at the time of deployment since all the user data is inside > the app bundle itself.What could be the major disadvantages of this > approach?Thanks & Regards AbhijeetDear cocoadev ! Get Yourself a cool, short > @in.com Email ID now! > _______________________________________________ > > 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/dave%40rudedog.org > > This email sent to d...@rudedog.org _______________________________________________ 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
