The document discusses Qt licensing options. Developers have a choice between the commercial Qt license from Nokia, which allows keeping all code private but restricts mixing licenses, or the LGPL license from the Free Software Foundation, which has some restrictions like requiring app code to remain private and dynamically linked to Qt. The document provides five factors to consider when choosing a license: external distribution needs, the target audience, modification plans, static vs dynamic linking, and calls to proprietary components.
+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
Â
Qt Licensing Explained
1. Qt Licensing
Explained
What are the Qt licensing options,
and what should you consider when
choosing the best Qt license for
your project?
Copyright Š 2009 Nokia Corporation and/or its subsidiary(-ies).
2. You have two licenses to choose from
Commercial LGPL
â˘âŻâ˘âŻLicensingby Nokia
Developed â˘âŻ Developed by Free
â˘âŻ Keep all code Software
private Foundation
â˘âŻ Keep your â˘âŻ Keep app code
distribution private, dynamically
licensing options linked to Qt
open â˘âŻ App licensing has
some restrictions
More details on the next slides
Copyright Š 2009 Nokia Corporation and/or its subsidiary(-ies).
3. What is the Qt Commercial license?
â˘âŻProprietary license developed by Nokia
â˘âŻAllows you to keep all code private
â˘âŻIncludes Qt standard support and updates
â˘âŻAllows you to choose license for distribution
⌠at time of distribution (more on the next slide)
Sorry, no mixing.
A Qt user cannot combine commercial and LGPL
in the same project. This is due to a restriction
in the Qt Commercial License.
Copyright Š 2009 Nokia Corporation and/or its subsidiary(-ies).
4. Choose your distribution licensingâŚ
at the time of distribution
â˘âŻNot sure of which license you should choose? Postpone the selection of
distribution licensing until the time of distribution.
â˘âŻThis is done by purchasing a commercial developer license and creating
an application that dynamically links to the Qt libraries. In this case you
can decide just prior to distribution whether to:
1.⯠Distribute your application with the commercially licensed Qt libraries, or
2.⯠Dynamically the application to the LGPL-licensed Qt libraries
â˘âŻThis also permits dual licensing of Qt-based applications
Not sure? Start commercial.
Keep your distribution licensing options open.
Copyright Š 2009 Nokia Corporation and/or its subsidiary(-ies).
5. What is the LGPL?
â˘âŻLGPL stands for GNU Lesser General Public License
â˘âŻA license agreement written and copyrighted by the Free Software
Foundation
â˘âŻNokia cannot modify the terms â it´s not our license.
â˘âŻThe LGPL is a âcopyleftâ open source software license that is less
restrictive than the GPL (GNU General Public License)
What does this mean for you?
You can freely use Qt under an LGPL license to
create proprietary applications that
dynamically link to the Qt libraries. (More later)
Copyright Š 2009 Nokia Corporation and/or its subsidiary(-ies).
6. There are five factors to consider
when selecting your license
1 2 3 4 5
We will cover each in more detail
in the coming slides.
Copyright Š 2009 Nokia Corporation and/or its subsidiary(-ies).
7. 1 Will you need to distribute your
application externally?
Copyright Š 2009 Nokia Corporation and/or its subsidiary(-ies).
8. 1 Will you need to distribute your
application externally?
â˘âŻThe requirements of the LGPL v. 2.1 only apply to externally distributed
applications BUT note that you cannot change this after development
has started due to a restriction in the Qt Commercial License Agreement.
â˘âŻThe LGPL only applies to externally distributed applications. If you are
using Qt to create an internal application, take adequate precautions to
make sure that the application is not distributed outside of the legal
entity. Otherwise, you will need to comply with the LGPL v. 2.1
obligations.
Copyright Š 2009 Nokia Corporation and/or its subsidiary(-ies).
9. 2 Who is your target audience?
Copyright Š 2009 Nokia Corporation and/or its subsidiary(-ies).
10. 2 Who is your target audience?
â˘âŻYou need to know if your target audience has restrictions against using
open source licensed software.
â˘âŻIf they do, then donât use Qt under the LGPL v. 2.1
â˘âŻIf your target audience will need to further modify Qt the LGPL may be a
good choice unless these modifications to Qt represent a userâs
commercial advantage and the user would not want to share them in
source code format with downstream recipients.
Copyright Š 2009 Nokia Corporation and/or its subsidiary(-ies).
11. 3 Will you need to modify Qt?
Copyright Š 2009 Nokia Corporation and/or its subsidiary(-ies).
12. 3 Will you need to modify Qt?
â˘âŻYou need to consider the implications regarding modification to Qt
carefully
â˘âŻIf you modify Qt, you will need to distribute these modifications in
source code format
Don´t want to share?
Choose commerical.
If you consider your modifications to represent a
âcompetitive advantageâ and you donât want to
distribute them in source code format, donât choose
the LGPL v. 2.1 license for Qt.
Copyright Š 2009 Nokia Corporation and/or its subsidiary(-ies).
13. 4 Will you need to statically link your
application to the Qt libraries in order to
optimize performance?
Copyright Š 2009 Nokia Corporation and/or its subsidiary(-ies).
14. 4 Will you need to statically link your
application to the Qt libraries in order to
optimize performance?
â˘âŻThere is debate within the legal and open source communities as to
whether static linking is permitted under the LGPL v. 2.1 license
â˘âŻThis is due to an inconsistency in the LGPL v. 2.1 license itself regarding
the definition of âworks based on the Libraryâ as the Library and
derivative works of the library.
â˘âŻExecutables may be considered to be derivative works and this could
result in the need to share the application source code
Tune out the static.
Our recommendation is that you don´t statically link
to the Qt libraries if you´re using the LGPL license.
Copyright Š 2009 Nokia Corporation and/or its subsidiary(-ies).
15. 5 Is the software architecture such that Qt
will need to make calls to a proprietary
component that is not âstandardâ?
Copyright Š 2009 Nokia Corporation and/or its subsidiary(-ies).
16. 5 Is the software architecture such that Qt will
need to make calls to a proprietary component
that is not âstandardâ?
â˘âŻIf Qt will make calls to a non-standard proprietary component you could
have a license incompatibility if such proprietary component does not
permit you to redistribute it.
â˘âŻSection 6 states that ââŚthe required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it.â
â˘âŻMaterials ânormally distributed (in either source or binary form) with the
major components (compiler, kernel, and so on) of the operating system
on which the executable runsâ are exempted, unless the component
itself accompanies the executable.
Copyright Š 2009 Nokia Corporation and/or its subsidiary(-ies).
17. Summary/More info
â˘âŻNokia offers customers licensing options
â˘âŻGet your legal team involved early to make the right decision
â˘âŻUnderstand your obligations with LGPL
â˘âŻThe Qt Commercial License give you options and full control
Licensing details at http://qt.nokia.com/licensing
Think commercial licensing is for you? Contact sales.
Copyright Š 2009 Nokia Corporation and/or its subsidiary(-ies).