André:
> IANAL, but I don't see the ambiguity in the requirements, ...
You don't find these paragraphs from LGPL 2.1, if not ambiguous,
at least "interesting"?
When a "work that uses the Library" uses material from a
header file that is part of the Library, the object code
for the work may be a derivative work of the Library even
though the source code is not. Whether this is true is
especially significant if the work can be linked without
the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined
by law.
If such an object file uses only numerical parameters,
data structure layouts and accessors, and small macros
and small inline functions (ten lines or less in length),
then the use of the object file is unrestricted, regardless
of whether it is legally a derivative work. (Executables
containing this object code plus portions of the Library
will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library,
you may distribute the object code for the work under the
terms of Section 6. Any executables containing that work
also fall under Section 6, whether or not they are linked
directly with the Library itself.
Do you study your developed code to ensure that it only uses
"small macros and small inline functions (ten lines or less
in length)"?
Atlant
FYI, here's the equivalent language from LGPL 3.0:
3. Object Code Incorporating Material from Library Header Files.
The object code form of an Application may incorporate material
from a header file that is part of the Library. You may convey
such object code under terms of your choice, provided that, if
the incorporated material is not limited to numerical parameters,
data structure layouts and accessors, or small macros, inline
functions and templates (ten or fewer lines in length), you do
both of the following:
a) Give prominent notice with each copy of the object code that
the Library is used in it and that the Library and its use are
covered by this License.
b) Accompany the object code with a copy of the GNU GPL and this
license document.
-----Original Message-----
From: interest-bounces+aschmidt=dekaresearch....@qt-project.org
[mailto:interest-bounces+aschmidt=dekaresearch....@qt-project.org] On Behalf Of
André Somers
Sent: Tuesday, August 14, 2012 11:12 AM
To: interest@qt-project.org
Subject: Re: [Interest] Digia to acquire Qt from Nokia
Op 14-8-2012 17:06, BRM schreef:
>> To: BRM <bm_witn...@yahoo.com>
>> Subject: Re: [Interest] Digia to acquire Qt from Nokia
>> 14.08.2012, 18:50, "BRM" <bm_witn...@yahoo.com>:
>>> most of the commercial licensees are sticking with the commercial license
>> because of the ambiguity
>>> with the LGPL and how to apply it; and the fact that while Nokia did do
>> that, they have not provided any
>>> clarity to its use.
>> ... while developers of proprietary software, which are not commercial
>> licensees, use LGPL license :)
>>
> Some may yes, but I think the general ambiguity left by the LGPL requirements
> still pushes most towards commercial licenses.
> So I don't think it has really changed anything in terms of business.
>
> I could be wrong - only someone familiar with the various deals within
> Nokia/Digia could really answer that, but that won't likely happen.
IANAL, but I don't see the ambiguity in the requirements, and our
company is using Qt under LGPL. And no, that's not not a small hobby
project.
André
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
This e-mail and the information, including any attachments, it contains are
intended to be a confidential communication only to the person or entity to
whom it is addressed and may contain information that is privileged. If the
reader of this message is not the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this communication is
strictly prohibited. If you have received this communication in error, please
immediately notify the sender and destroy the original message.
Thank you.
Please consider the environment before printing this email.
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
