Using qt for a commercial application on windows (LGPL)
-
@JKSH said in Using qt for a commercial application on windows (LGPL):
These paths are not mutually exclusive.
Thank you anyway, but i don't agree with you. If i am already have in-depth understanding on how to use LGPL'ed software in my project, i don`t need some legal protection and vice versa
-
@Jo-Jo
In that case I do not understand why you are still asking questions here? If you have "in-depth understanding on how to use LGPL'ed software" then you already have your answers.Nobody here is going to give you any cast iron guarantees about interpretations, legal issues, how The Qt Company might or might not act, or similar. At best they will just refer you to items online or courses of action to take, as they have been doing.
If you wish you may ask The Qt Company about your concerns. My guess --- no more than that --- is that they will advise you to purchase a commercial licence if you want to be "sure". If you adopt the LGPL approach you will find out whether The Qt Company has any objections if they contact you or take you to court. That is how legal matters work, not even a legal person can guarantee you there will be no issues, they can only express opinions, that is why we have courts and legal proceedings, to "test" law or interpretation.
@JonB said in Using qt for a commercial application on windows (LGPL):
If you have "in-depth understanding on how to use LGPL'ed software" then you already have your answers.
No, i dont have "in-depth understanding on how to use LGPL'ed software". I think you've lost the context of this phrase.
@JonB said in Using qt for a commercial application on windows (LGPL):
Nobody here is going to give you any cast iron guarantees about interpretations, legal issues, how The Qt Company might or might not act, or similar.
I understand that. The main thing for me is to understand how to approach this issue correctly. Some users of this forum suggest listening to what some people say, others recommend contacting a lawyer. There is no standard way, and there is no example of successful use of LGPL for commercial closed source software for Windows.
-
@Jo-Jo I'm not sure what kind of answer you expect to get in a user forum like this? Nobody here is a lawyer.
@jsulm said in Using qt for a commercial application on windows (LGPL):
I'm not sure what kind of answer you expect to get in a user forum like this?
I wonder why some people advise to contact a lawyer while others advise to listen to certain people on the internet. Who is right?
-
A bit late to the party!
The most comprehensive and useful presentation that I know on this topic is one from Burkhard Stubert, entitled "Making Qt Systems Comply To LGPL Version 3" https://www.youtube.com/watch?v=bwTlCBbB3RY It also mentions a few cases towards the end where companies did not comply properly at first.
@Jo-Jo said in Using qt for a commercial application on windows (LGPL):
After all the messages, unfortunately, I still couldn't get a concrete answer about whether it is possible to use Qt for Windows app with the LGPL license for free and safely or not.
The presentation above discusses how to do it safely on embedded systems. Everything that you learn there can be applied to Windows too (and it's arguably even simpler on desktop systems).
@JKSH said in Using qt for a commercial application on windows (LGPL):
Now i am watching this video and can`t understand this detail: At the 6:30, video says: "display copyright notices of Qt libraries and license texsts lf LGPLv3 and GPL in Application's GUI (4c)".
- I am familiar with LGPLv3 and GPL text, but where i can found "copyright notices of Qt libraries"?
- What does 4c mean?
-
@JonB said in Using qt for a commercial application on windows (LGPL):
If you have "in-depth understanding on how to use LGPL'ed software" then you already have your answers.
No, i dont have "in-depth understanding on how to use LGPL'ed software". I think you've lost the context of this phrase.
@JonB said in Using qt for a commercial application on windows (LGPL):
Nobody here is going to give you any cast iron guarantees about interpretations, legal issues, how The Qt Company might or might not act, or similar.
I understand that. The main thing for me is to understand how to approach this issue correctly. Some users of this forum suggest listening to what some people say, others recommend contacting a lawyer. There is no standard way, and there is no example of successful use of LGPL for commercial closed source software for Windows.
@Jo-Jo I pointed you to Blackmagic Design.
As for who is right ? Both are. Inform yourself with people having real experience in managing software and projects using open source licenses and consult a lawyer to ensure you are doing things correctly. Especially when working in fields like medical.
-
@Jo-Jo I pointed you to Blackmagic Design.
As for who is right ? Both are. Inform yourself with people having real experience in managing software and projects using open source licenses and consult a lawyer to ensure you are doing things correctly. Especially when working in fields like medical.
@SGaist said in Using qt for a commercial application on windows (LGPL):
As for who is right ? Both are. Inform yourself with people having real experience in managing software and projects using open source licenses and consult a lawyer to ensure you are doing things correctly
I got you, thanks! But I don't really understand what I should talk about with a lawyer. If, for example, I ask him whether it is necessary to link dynamically with Qt libraries, he probably won't understand me, because he most likely doesn't know programming. How should I talk to him then?
-
@SGaist said in Using qt for a commercial application on windows (LGPL):
As for who is right ? Both are. Inform yourself with people having real experience in managing software and projects using open source licenses and consult a lawyer to ensure you are doing things correctly
I got you, thanks! But I don't really understand what I should talk about with a lawyer. If, for example, I ask him whether it is necessary to link dynamically with Qt libraries, he probably won't understand me, because he most likely doesn't know programming. How should I talk to him then?
-
There are law firms specialized on IT/software development, licensing, eCommerce, data privacy etc...
You don't talk to a lawyer's office that would also help you with your divorce ;-)@Pl45m4 said in Using qt for a commercial application on windows (LGPL):
There are law firms specialized on IT/software development, licensing, eCommerce, data privacy etc...
Thank you!
https://www.youtube.com/watch?v=bwTlCBbB3RY
This video says to "display copyright notices of Qt libraries and license texsts lf LGPLv3 and GPL in Application's GUI". Where can I find copyright notices of Qt libraries? -
@JKSH said in Using qt for a commercial application on windows (LGPL):
Now i am watching this video and can`t understand this detail: At the 6:30, video says: "display copyright notices of Qt libraries and license texsts lf LGPLv3 and GPL in Application's GUI (4c)".
- I am familiar with LGPLv3 and GPL text, but where i can found "copyright notices of Qt libraries"?
- What does 4c mean?
@Jo-Jo said in Using qt for a commercial application on windows (LGPL):
@JKSH said in Using qt for a commercial application on windows (LGPL):
Now i am watching this video and can`t understand this detail: At the 6:30, video says: "display copyright notices of Qt libraries and license texsts lf LGPLv3 and GPL in Application's GUI (4c)".
- I am familiar with LGPLv3 and GPL text, but where i can found "copyright notices of Qt libraries"?
- What does 4c mean?
-
See here for a definition of a "copyright notice": https://copyrightalliance.org/faqs/what-is-copyright-notice/
Then, in a Qt Widgets application, callQApplication::aboutQt()and you'll see this line near the bottom of the dialog: "Copyright (C) The Qt Company Ltd. and other contributors." -- just add the year of release and you'll have a notice that meets the definition given in the link above. -
"(4c)" in the presentation slide refers to section 4c of the actual LGPLv3 license (visit https://www.gnu.org/licenses/lgpl-3.0.en.html and scroll down to "4. Combined Works"). Ditto for the other tags in the slide ("4a", "4d1", etc.)
The presenter is rephrasing/simplifying/summarizing different parts of the license to make them easier to understand. He's citing the original parts so that viewers can check the actual license (for example, so that you can satisfy yourself that his statements align with the actual license)
-
@Jo-Jo said in Using qt for a commercial application on windows (LGPL):
@JKSH said in Using qt for a commercial application on windows (LGPL):
Now i am watching this video and can`t understand this detail: At the 6:30, video says: "display copyright notices of Qt libraries and license texsts lf LGPLv3 and GPL in Application's GUI (4c)".
- I am familiar with LGPLv3 and GPL text, but where i can found "copyright notices of Qt libraries"?
- What does 4c mean?
-
See here for a definition of a "copyright notice": https://copyrightalliance.org/faqs/what-is-copyright-notice/
Then, in a Qt Widgets application, callQApplication::aboutQt()and you'll see this line near the bottom of the dialog: "Copyright (C) The Qt Company Ltd. and other contributors." -- just add the year of release and you'll have a notice that meets the definition given in the link above. -
"(4c)" in the presentation slide refers to section 4c of the actual LGPLv3 license (visit https://www.gnu.org/licenses/lgpl-3.0.en.html and scroll down to "4. Combined Works"). Ditto for the other tags in the slide ("4a", "4d1", etc.)
The presenter is rephrasing/simplifying/summarizing different parts of the license to make them easier to understand. He's citing the original parts so that viewers can check the actual license (for example, so that you can satisfy yourself that his statements align with the actual license)
Thank you so much!
@JKSH said in Using qt for a commercial application on windows (LGPL):
just add the year of release and you'll have a notice that meets the definition given in the link above.
QApplication::aboutQt()Shows following text: "Copyright (C) 2023 The Qt Company Ltd and other contributors."
Should I leave 2023 or should I specify the year that was in effect when the current version of the app was released?
-
Thank you so much!
@JKSH said in Using qt for a commercial application on windows (LGPL):
just add the year of release and you'll have a notice that meets the definition given in the link above.
QApplication::aboutQt()Shows following text: "Copyright (C) 2023 The Qt Company Ltd and other contributors."
Should I leave 2023 or should I specify the year that was in effect when the current version of the app was released?
You're most welcome!
@Jo-Jo said in Using qt for a commercial application on windows (LGPL):
QApplication::aboutQt()Shows following text: "Copyright (C) 2023 The Qt Company Ltd and other contributors."
Should I leave 2023 or should I specify the year that was in effect when the current version of the app was released?
Depending on the version of Qt that you're using, 2023 might be incorrect: https://bugreports.qt.io/browse/QTBUG-121906
Personally, I would use the year that the particular version of Qt was released (because this particular copyright notice is about Qt, not about your app)
-
You're most welcome!
@Jo-Jo said in Using qt for a commercial application on windows (LGPL):
QApplication::aboutQt()Shows following text: "Copyright (C) 2023 The Qt Company Ltd and other contributors."
Should I leave 2023 or should I specify the year that was in effect when the current version of the app was released?
Depending on the version of Qt that you're using, 2023 might be incorrect: https://bugreports.qt.io/browse/QTBUG-121906
Personally, I would use the year that the particular version of Qt was released (because this particular copyright notice is about Qt, not about your app)
@JKSH said in Using qt for a commercial application on windows (LGPL):
Personally, I would use the year that the particular version of Qt was released (because this particular copyright notice is about Qt, not about your app)
I got you, thanks again!
-
Sorry, i have another question. In this video https://www.youtube.com/watch?v=bwTlCBbB3RY at the 18:20 he talking about "Displaying License and Copyright in GUI": It looks like for each module I need to specify the copyright (and not just the Qt copyright, but all the copyrights from all the source files in the module), the GPL/LGPL license text, modifications (if any), the used-license (what is that? Should we just show the LGPLv3 text when clicking on this menu or something else?). So I need to duplicate this information for each Qt module I will use and it is not enough to provide the common text for all modules once?
