Thanks for the answer. So I can incorporate QtRPT program with my application for the report generation part and redistribute it as a commercial solution? or there is some restrictions?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the answer. So I can incorporate QtRPT program with my application for the report generation part and redistribute it as a commercial solution? or there is some restrictions?
The problem with qtrpt and LGPL is the that you don't have a dynamic library.
With LGPL you have to give the source of qtrpt to everyone who use your software and ask for the code because you have to grant the right for changing the qtrpt source code.
This is one of the main thought behind LGPL.
With the default build option you don't have a dynamic library. If you build the qtrpt source direct (static) in your project you have give the source of your program to every user who ask for changeing the qtrpt source. Otherwhise you violate the LGPL.
Apache 2.0 would be the better license because you have to write/show a text that you use a library under apache 2.0 license and it's not necessary to open the source or give it to the user.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So you can mix the libraries and software lisense in your software what ever you want as long the LGPL part is dynamically linked.
Btw: you can do with your software what you want and relisense it under any lisense you want - it's yours. ;-)
One exception: if you use a GPL (only) library you have to open your source.
"For you personally than the license GPL/LGPG is bad?"
No, not the LGPL, because I know how to create a dll from a c++ project.
But for all other here could it be a problem because they violate the lisense
if they want to make a commercial application and (&&) include the QtRPT
source by including the qtrpt.pri direct into their project.
If you like I can give you the few files for creating a dll - they habe to be
under LGPL because the files are derived work form your project. In my project
I include only a header file which is a counter part of the exported functions
of/from the dll.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks, I know how to create a dll. Well I completely understand the situation coz they must open code but it undesirable. But if I make the dll and change the license then I violate the Qt license, isnt it?
Last edit: aliks-os 2014-10-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can make closed source projects with Qt without violating the Qt opensource licence, as long as you link dynamicaly to the Qt libs.
there is problem, you are using the zint project for the barcodes this project is licenced as GPL so you are required to open all source using this lib. the only way to make this project available in LGPL is by removing the barcode generator or use a different one licenced in LGPL
Last edit: StrikeByte 2014-10-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I love this project, so i hope you will keep it as LGPL.
For my project I changed the report designer and creator so that it doesn't use zint (no barcode support)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For a long time the QtRPT project is distributed under the LGPL license. This license allows you to dynamically link with your source code. In order to facilitate the user to use QtRPT and allow to produce statically linking, I decided to change the Apache 2.0 license.
License Apache 2.0 more permissive compared to LGPL, I hope that the transition will not create problems for you
Please note that QtRPT to generate bar code uses the Zint library, which is distributed under license GPL, in this case, you must use your project is also under this license or disable the use of the Zint library.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, what would be the QtRPT licencing terms?
Because I would like to use it with my program.
I think for LGPL it is nessesary (better) to release it as a shared lib, if someone want use it in commercial programs.
Thanks for the answer. So I can incorporate QtRPT program with my application for the report generation part and redistribute it as a commercial solution? or there is some restrictions?
I hope will be ready during some days
Ok no problem, thank you!
The problem with qtrpt and LGPL is the that you don't have a dynamic library.
With LGPL you have to give the source of qtrpt to everyone who use your software and ask for the code because you have to grant the right for changing the qtrpt source code.
This is one of the main thought behind LGPL.
With the default build option you don't have a dynamic library. If you build the qtrpt source direct (static) in your project you have give the source of your program to every user who ask for changeing the qtrpt source. Otherwhise you violate the LGPL.
Apache 2.0 would be the better license because you have to write/show a text that you use a library under apache 2.0 license and it's not necessary to open the source or give it to the user.
I use LGPL/GPL the license as I use Qt as under this licenses. Respectively I can't use another of the license (for example Apache 2.0), it is right?
Proceeding from logic of LGPL/GPL, users who use QtRPT also have to provide access to an source code of the program.
Concerning static build of QtRPT, I can't make it as I don't use the commercial Qt version.
http://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License
So you can mix the libraries and software lisense in your software what ever you want as long the LGPL part is dynamically linked.
Btw: you can do with your software what you want and relisense it under any lisense you want - it's yours. ;-)
One exception: if you use a GPL (only) library you have to open your source.
This is a list of differenct qt project with different lisense
http://qt-project.org/wiki/Category:Add-ons
For all the other user of your library: if you want to use qtrpt in your project you have to use/build a dll or release the source of your software.
Frank
For you personally than the license GPL/LGPG is bad?
You don't want to open the source code? And want to use opensource?
"For you personally than the license GPL/LGPG is bad?"
No, not the LGPL, because I know how to create a dll from a c++ project.
But for all other here could it be a problem because they violate the lisense
if they want to make a commercial application and (&&) include the QtRPT
source by including the qtrpt.pri direct into their project.
If you like I can give you the few files for creating a dll - they habe to be
under LGPL because the files are derived work form your project. In my project
I include only a header file which is a counter part of the exported functions
of/from the dll.
Thanks, I know how to create a dll. Well I completely understand the situation coz they must open code but it undesirable. But if I make the dll and change the license then I violate the Qt license, isnt it?
Last edit: aliks-os 2014-10-01
You can make closed source projects with Qt without violating the Qt opensource licence, as long as you link dynamicaly to the Qt libs.
there is problem, you are using the zint project for the barcodes this project is licenced as GPL so you are required to open all source using this lib. the only way to make this project available in LGPL is by removing the barcode generator or use a different one licenced in LGPL
Last edit: StrikeByte 2014-10-30
Many thanks for an explanation!
I will think that it is possible to undertake in this case.
I love this project, so i hope you will keep it as LGPL.
For my project I changed the report designer and creator so that it doesn't use zint (no barcode support)
There can be it and a way out, not to include zint in structure of the project, and to suggest users to download it separately and to use if necessary
That would be super
Dear users of QtRPT
For a long time the QtRPT project is distributed under the LGPL license. This license allows you to dynamically link with your source code. In order to facilitate the user to use QtRPT and allow to produce statically linking, I decided to change the Apache 2.0 license.
License Apache 2.0 more permissive compared to LGPL, I hope that the transition will not create problems for you
Please note that QtRPT to generate bar code uses the Zint library, which is distributed under license GPL, in this case, you must use your project is also under this license or disable the use of the Zint library.