Are results of Qt Creator (ex. .UI file) also under GPL?
-
Dear Qt Guru,
I have been googling about license stuff for hours, but couldn't find answer. My case is below:
Qt Creator is GPLv3. I designed a GUI using Qt Creator and I used the result(such as .UI file) in my embedded application. Then my application is also under GPLv3? Do I have to open my whole application to public? -
Hi and welcome to devnet,
Qt Creator is an IDE, its license has nothing to do with what you edit with it.
However, the version of Qt does. If you are using the GPL release then you have to abide by that licence.
-
Hi and welcome to devnet,
Qt Creator is an IDE, its license has nothing to do with what you edit with it.
However, the version of Qt does. If you are using the GPL release then you have to abide by that licence.
Thanks for your reply @SGaist.
"Qt Creator is an IDE, its license has nothing to do with what you edit with it."
=> I've found the "the GNU General Public License version 3, annotated with The Qt Company GPL Exception 1.0: Exception 1:"
According to this exception, I think your comment is right."However, the version of Qt does. If you are using the GPL release then you have to abide by that license."
=> I also found a blog https://www.qt.io/blog/2016/01/13/new-agreement-with-the-kde-free-qt-foundation
=> Based on the above blog, I'm going to apply and release my code with Qt 5.6. At that time(Qt 5.6), most of the Qt modules were LGPLv2.1. If I follow the rules of LGPL and dynamic linking style, I don't have to open my whole code, right?Thank you inadvance
-
Thanks for your reply @SGaist.
"Qt Creator is an IDE, its license has nothing to do with what you edit with it."
=> I've found the "the GNU General Public License version 3, annotated with The Qt Company GPL Exception 1.0: Exception 1:"
According to this exception, I think your comment is right."However, the version of Qt does. If you are using the GPL release then you have to abide by that license."
=> I also found a blog https://www.qt.io/blog/2016/01/13/new-agreement-with-the-kde-free-qt-foundation
=> Based on the above blog, I'm going to apply and release my code with Qt 5.6. At that time(Qt 5.6), most of the Qt modules were LGPLv2.1. If I follow the rules of LGPL and dynamic linking style, I don't have to open my whole code, right?Thank you inadvance
@St-Pio said in Are results of Qt Creator (ex. .UI file) also under GPL?:
LGPL and dynamic linking style, I don't have to open my whole code, right?
right
Same for LGPLv3 with the exception that you have to provide object files (not source code!) to your users, so they can relink your app with their own Qt libs.
-
@St-Pio said in Are results of Qt Creator (ex. .UI file) also under GPL?:
LGPL and dynamic linking style, I don't have to open my whole code, right?
right
Same for LGPLv3 with the exception that you have to provide object files (not source code!) to your users, so they can relink your app with their own Qt libs.
@jsulm said in Are results of Qt Creator (ex. .UI file) also under GPL?:
@St-Pio said in Are results of Qt Creator (ex. .UI file) also under GPL?:
LGPL and dynamic linking style, I don't have to open my whole code, right?
right
Same for LGPLv3 with the exception that you have to provide object files (not source code!) to your users, so they can relink your app with their own Qt libs.
AFAIK, providing objects is only needed when doing static linking. When using dynamic linking, you can just swap libraries as you wish.
