On Wednesday, April 7, 2010, Jens Alfke <j...@mooseyard.com> wrote: > > FYI to the OP: If you haven't worked with LGPL code before, be aware that you > must build it into a separate dynamic library or framework that you can > bundle inside your app. Statically linking the code into your app violates > the LGPL license, unless you also release your entire app under the LGPL. > (Unfortunately this makes using LGPL code in iPhone apps virtually > impossible, but that's probably not an issue in this case...)
Statically linking the code into your app does not automatically violate the LGPL, although it does make it harder to comply. The key requirement of the LGPL is that end users must be able to use your app with a copy of the library that they built themselves. If you liked the library dynamically then this is easy since they can just pull it out of the app and put in their own build. For static linking it's harder, but doable. The standard technique is to make available the object files (.o files) from your application. These can be linked with a new copy of the static library to produce a new copy of the app that uses a custom build of the library, thus fulfilling that LGPL requirement. Mike _______________________________________________ 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
