[Qt-interest] Licensing

[Jeroen De Wachter]

There's a whole thread on this mailing list regarding that subject 
(Thiago's post was one message in a long list)
I was about to refer to it as well.

Kind regards,

Jeroen

Jan wrote:
> Static vs. dynamic was discussed here as well
> A response from nokia was posted by thiago:
>
> http://lists.trolltech.com/pipermail/qt-interest/2009-December/016090.html
>
> In short: There is no clear Yes or No. But they suggest to use dynamic 
> linking with LGPL'd Qt.
>
> Jan
>
> Am 02.06.2010 14:39, schrieb Kustaa Nyholm:
>   
>>> this nice gpl,lgpl and commercial discussions...
>>> i repeat a statement already mentioned in this thread:
>>> don't trust anyone telling you something about how to behave concerning law
>>> just trust your paid lawyer.
>>>       
>> Well, listening to a lawyer is good, but most lawyers don't pay the bill
>> and suffer the consequences if the court decided against you in a dispute.
>> So in the end it is down to the organization or individual to decide
>> what to trust and what not to trust.
>>     
>>>   AS LONG AS you link dynamically to all lgpl code.
>>>       
>> Dynamic or static linking is no issue here, LGPL allows both.
>>
>> Section 6 applies to what has been discussed here ie LGPL library and closed
>> source application delivered as an executable.
>>
>> There it says (6a) that if you distribute statically linked application
>> you also need to distribute it in un-linked form so that the user
>> can (re)link it with a modified (improved or different) version
>> of the library, if they want. And 6c says that you don't even
>> have to distribute the un-linked form, it is enough if you
>> promise to deliver it on request.
>>
>> 6b refers to dynamic linking allowing distribution of the library alongside
>> with a dynamically linked application code, but it is worth noting that
>> section 5 clearly spells out that an application compiled against the
>> library falls outside the scope of the license and thus there is nothing in
>> the LGPL license to stop distribution of dynamically linked application code
>> in any shape or form as long as it does not contain the library.
>>
>> Worth noting is that the last two paragraphs of the section 6 require the
>> distribution of the tools and libraries required to (re)link the application
>> unless they are normally distributed with the OS.
>>
>> This may cause problems if you use libraries or tools that do not allow
>> redistribution. For example I don't think Windows comes with a linker
>> so static linking might require you to distribute the linker which
>> might not be possible if you use M$ tools. On the other hand if you
>> use Free tools such as MinGW you might be able to evoke 6c on them.
>>
>> br Kusti
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Qt-interest mailing list
>> Qt-interest at trolltech.com
>> http://lists.trolltech.com/mailman/listinfo/qt-interest
>>
>>     
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-interest
>
>   



DISCLAIMER:
Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.