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

[Thiago Macieira]

On Friday, 2 de September de 2011 20:32:14 NoRulez wrote:
> I had also one question about this problem.
> 
> Why I must distribute my app.

You don't have to give your app to anyone if you don't want to.

If you meant to ask "why must I distribute Qt with my app", see below.

> 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.

That's not correct. You must still provide the Qt sources. The LGPLv2.1 was 
written before the Internet became important, so it doesn't account for it.

Probably just giving the download URL from the Qt official website is enough to 
satisfy the spirit of the license.

> Is this right or wrong? When can I use the LGPL version for commercial
> usage, only when I use the dynamic libraries?

You can always use the LGPL or the GPL for commercial use. It's a myth that 
they forbid commercialisation.

But they do come with strings attached. Please read them to understand what it 
means to you.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20110902/a2c944b7/attachment.bin