> On Jan 26, 2016, at 1:17 PM, Britt Durbrow > <bdurb...@rattlesnakehillsoftworks.com> wrote: > > I would consider a: packaging a version of the library in your resources; and > loading that if there is not one in the app’s Application Support folder
Loading a library at runtime is somewhat awkward, because instead of being able to use its symbols directly you have to look them up by name (with function calls like dlsym) and call them through function pointers. Also, are sandboxed apps allowed to load libraries that are outside of their app bundle? IMHO putting the library inside your app bundle is enough to abide by the terms of the license. It’s not like a lot of actual users are going to be replacing the library, so there’s no point going to more work to make it easier. :) —Jens _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
