That’s outside the purview of the LGPL, I think. You simply have to make the code available for the user TO BE ABLE to relink if so desired. It’s not your responsibility to make sure the user has an appropriate development environment, etc. The code doesn’t have to be distributed with the application, just a notice linking to a relatively-permanent location where those files can be found.
That’s my understanding, at least.
Scott
From: coreaudio-api-bounces+scott=email@hidden [mailto:coreaudio-api-bounces+scott=email@hidden] On Behalf Of Paul Davis
Sent: Tuesday, July 17, 2012 2:57 PM
To: Kevin Dixon
Cc: coreaudio-api
Subject: Re: What's involved streaming audio to disk as mp3 in iOS
On Tue, Jul 17, 2012 at 3:45 PM, Kevin Dixon <email@hidden> wrote:
This thread (http://answers.google.com/answers/threadview/id/439136.html)
has a good discussion of LGPL and static linking.
If you link statically (which you must for iOS apps), you can
distribute your .o and .h files in order to comply with the
stipulations of the license.
how would the user manage a relink for the iOS platform?