Re: Alternative Location of Cocoa ID3 Framework??
Re: Alternative Location of Cocoa ID3 Framework??
- Subject: Re: Alternative Location of Cocoa ID3 Framework??
- From: Michael Ash <email@hidden>
- Date: Wed, 7 Apr 2010 15:26:12 -0400
On Wednesday, April 7, 2010, Jens Alfke <email@hidden> 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 (email@hidden)
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:
This email sent to email@hidden