[Qt-interest] Legal question: Qt IOS static linking

[Konstantin Tokarev]

04.09.2011, 16:01, "Ross Bencina" <rossb-lists at audiomulch.com>:
> On 3/09/2011 4:32 AM, NoRulez wrote:
>
>>  Why I must distribute my app. I thought that it would be a problem
>>  when I change the sources from Qt, but when I create static libraries
>>  then I don't touch the sources, so for my understanding I doesn't need
>>  to distribute anything from my app.
>
> My (limited) understanding is that there are really two "freedom" issues
> with unmodified LGPL:
>
> 1. As you suggest above, if you change the sources to Qt you are
> requeired to release those changes. You are also, in some sense,
> required to ensure that your end-users can access the Qt sources whether
> you changed them or not.
>
> 2. The end-user needs to be able to take your modified Qt sources, fix a
> bug in them, and then relink your app with the modified and user-patched
> sources. In other words, you get to keep your source code closed, but
> people still need to be able to link your object code with their own
> modified LGPL sources.
>
> So to answer your question: case (2) is why you must distribute .o files
> from your app if you don't support dynamic linking of GPL code.

See section 6c. 

"  c) Accompany the work with a written offer, valid for at
    least three years, to give the same user the materials
    specified in Subsection 6a, above, for a charge no more
    than the cost of performing this distribution."

So you don't have to redistribute object files if you are not asked about it,
if you promise that it's possible to ask them.

-- 
Regards,
Konstantin