Do I have to pay money?
-
@kshegunov said in Do I have to pay money?:
I'm pretty sure this also applies to the LGPL.
You have to provide the modifications you did to the LGPL dependencies you are using but you are not required to upstream them.
@SGaist said in Do I have to pay money?:
You have to provide the modifications you did to the LGPL dependencies you are using but you are not required to upstream them.
Hm, okay. I was wrong then.
Read and abide by the Qt Code of Conduct
-
@SGaist said in Do I have to pay money?:
You have to provide the modifications you did to the LGPL dependencies you are using but you are not required to upstream them.
Hm, okay. I was wrong then.
@kshegunov said in Do I have to pay money?:
@SGaist said in Do I have to pay money?:
You have to provide the modifications you did to the LGPL dependencies you are using but you are not required to upstream them.
Hm, okay. I was wrong then.
Not completely, upstreaming is the nice thing to do so everybody can benefit from your changes. However, it can happen that some features might not align with a project goal hence they might not be suitable for inclusion.
You might also be using a library which is working fine but is currently not maintained, etc.Interested in AI ? www.idiap.ch
Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct -
@kshegunov said in Do I have to pay money?:
@SGaist said in Do I have to pay money?:
You have to provide the modifications you did to the LGPL dependencies you are using but you are not required to upstream them.
Hm, okay. I was wrong then.
Not completely, upstreaming is the nice thing to do so everybody can benefit from your changes. However, it can happen that some features might not align with a project goal hence they might not be suitable for inclusion.
You might also be using a library which is working fine but is currently not maintained, etc. -
Reading this thread I was thinking about the situation like this:
For whatever reason I want to use GPL version of Qt (for instance because WebAssembly isn't available under LGPL) in my application (which in a sense is "proprietary"). Now, I also use proprietary library which is optional dependency (if not used the program would be usable but could have some usability issues in some specific areas). AFAIK my application needs to be also GPL (or could I use another license???). But from what I've read in the FAQ GPL application must not link to the proprietary library.
So what are my options?
-
Reading this thread I was thinking about the situation like this:
For whatever reason I want to use GPL version of Qt (for instance because WebAssembly isn't available under LGPL) in my application (which in a sense is "proprietary"). Now, I also use proprietary library which is optional dependency (if not used the program would be usable but could have some usability issues in some specific areas). AFAIK my application needs to be also GPL (or could I use another license???). But from what I've read in the FAQ GPL application must not link to the proprietary library.
So what are my options?
@Trigve said in Do I have to pay money?:
AFAIK my application needs to be also GPL
Correct. If your application links to a GPL library, then your application must also be released under the GPL license.
from what I've read in the FAQ GPL application must not link to the proprietary library.
Correct. A GPL application can link to libraries whose licenses that are compatible with GPL (see https://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses for a list of compatible licenses). However, proprietary licenses are not compatible with GPL, so proprietary libraries cannot be used in a GPL application.
Now, I also use proprietary library which is optional dependency (if not used the program would be usable but could have some usability issues in some specific areas)
If removing the library creates some usability issues, then I'm not convinced that it's truly optional... See @Chris-Kawa's link below about plugins.
So what are my options?
Some options include:
- Get a commercial license for all the libraries you want to use. This way, you obtain the rights for your application to link to all of those libraries. Note: Using this option, you cannot release your application under a free software license.
- Convince the owners of the proprietary library to release their library under a GPL-compatible license too. This way, your GPL application can link to it.
- Replace the proprietary library with a different one which is GPL-compatible. This way, your GPL application can link to it.
Qt Doc Search for browsers: forum.qt.io/topic/35616/web-browser-extension-for-improved-doc-searches
-
@Trigve said in Do I have to pay money?:
AFAIK my application needs to be also GPL
Correct. If your application links to a GPL library, then your application must also be released under the GPL license.
from what I've read in the FAQ GPL application must not link to the proprietary library.
Correct. A GPL application can link to libraries whose licenses that are compatible with GPL (see https://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses for a list of compatible licenses). However, proprietary licenses are not compatible with GPL, so proprietary libraries cannot be used in a GPL application.
Now, I also use proprietary library which is optional dependency (if not used the program would be usable but could have some usability issues in some specific areas)
If removing the library creates some usability issues, then I'm not convinced that it's truly optional... See @Chris-Kawa's link below about plugins.
So what are my options?
Some options include:
- Get a commercial license for all the libraries you want to use. This way, you obtain the rights for your application to link to all of those libraries. Note: Using this option, you cannot release your application under a free software license.
- Convince the owners of the proprietary library to release their library under a GPL-compatible license too. This way, your GPL application can link to it.
- Replace the proprietary library with a different one which is GPL-compatible. This way, your GPL application can link to it.
@JKSH
Programs can "interact" with each other in a myriad of ways. For example, they might use sockets or files to exchange information. You can mix GPL with commercial/proprietary in this way, because everyone does it.So... why can't I/the OP provide a non-linked, on-demand dynamic library for his optional dependency features, which he does LoadLibrary/GetProcAddress-type interface to allow that kind of "interaction"?
-
@JKSH
Programs can "interact" with each other in a myriad of ways. For example, they might use sockets or files to exchange information. You can mix GPL with commercial/proprietary in this way, because everyone does it.So... why can't I/the OP provide a non-linked, on-demand dynamic library for his optional dependency features, which he does LoadLibrary/GetProcAddress-type interface to allow that kind of "interaction"?
@JonB said in Do I have to pay money?:
So... why can't I/the OP provide a non-linked, on-demand dynamic library for his optional dependency features,
Because dynamic linking is still linking. FSF considers it "cheating" and treats plugins, shared memory etc. to fall under a single combined program definition and thus also require such plugins to be GPL compatible. See source.
Keep in mind that GPL is aggressively viral and intentionally so and thus trying to "workaround" it in any way is strictly against its idea.
-
@JKSH
Programs can "interact" with each other in a myriad of ways. For example, they might use sockets or files to exchange information. You can mix GPL with commercial/proprietary in this way, because everyone does it.So... why can't I/the OP provide a non-linked, on-demand dynamic library for his optional dependency features, which he does LoadLibrary/GetProcAddress-type interface to allow that kind of "interaction"?
@JonB said in Do I have to pay money?:
@JKSH
Programs can "interact" with each other in a myriad of ways. For example, they might use sockets or files to exchange information. You can mix GPL with commercial/proprietary in this wayIf the 2 components are truly independent, then sure you can "mix" them this way.
However, @Trigve's description does not sound like independent components so @Chris-Kawa's point applies.
-
@JonB said in Do I have to pay money?:
@JKSH
Programs can "interact" with each other in a myriad of ways. For example, they might use sockets or files to exchange information. You can mix GPL with commercial/proprietary in this wayIf the 2 components are truly independent, then sure you can "mix" them this way.
However, @Trigve's description does not sound like independent components so @Chris-Kawa's point applies.
@JKSH said in Do I have to pay money?:
If the 2 components are truly independent, then sure you can "mix" them this way.
However, @Trigve's description does not sound like independent components so @Chris-Kawa's point applies.
In my case the optional dependency is library used for viewing some documents, which isn't necessary altogether, because I could render the document as .pdf and use system viewer (in my case the "proprietary dependency" contains also an executable which encapsulate the library so in this case I could use the .exe instead of library and should be OK, AFAIK).
-
@JKSH said in Do I have to pay money?:
If the 2 components are truly independent, then sure you can "mix" them this way.
However, @Trigve's description does not sound like independent components so @Chris-Kawa's point applies.
In my case the optional dependency is library used for viewing some documents, which isn't necessary altogether, because I could render the document as .pdf and use system viewer (in my case the "proprietary dependency" contains also an executable which encapsulate the library so in this case I could use the .exe instead of library and should be OK, AFAIK).
-
@JKSH said in Do I have to pay money?:
If the 2 components are truly independent, then sure you can "mix" them this way.
However, @Trigve's description does not sound like independent components so @Chris-Kawa's point applies.
In my case the optional dependency is library used for viewing some documents, which isn't necessary altogether, because I could render the document as .pdf and use system viewer (in my case the "proprietary dependency" contains also an executable which encapsulate the library so in this case I could use the .exe instead of library and should be OK, AFAIK).
@Trigve said in Do I have to pay money?:
In my case the optional dependency is library used for viewing some documents, which isn't necessary altogether, because I could render the document as .pdf and use system viewer
Does this mean you've found a way to resolve the "usability issues" you mentioned before, without depending on the proprietary library/application? If so, then I don't see a problem -- You can certainly distribute a GPL app which produces PDF files and launches the system viewer (via the
Qt PDFmodule andQDesktopServicesclass, I presume?) -
@Trigve said in Do I have to pay money?:
In my case the optional dependency is library used for viewing some documents, which isn't necessary altogether, because I could render the document as .pdf and use system viewer
Does this mean you've found a way to resolve the "usability issues" you mentioned before, without depending on the proprietary library/application? If so, then I don't see a problem -- You can certainly distribute a GPL app which produces PDF files and launches the system viewer (via the
Qt PDFmodule andQDesktopServicesclass, I presume?)@JKSH said in Do I have to pay money?:
Does this mean you've found a way to resolve the "usability issues" you mentioned before, without depending on the proprietary library/application?
Usability issue is that you either use proprietary viewer with more functionality or else convert to .pdf and use system viewer. What I had in mind was that application could either use or not proprietary library (if one has a license), which should be resolved at build time. But in this case the application cannot be GPL.
-
This post is deleted!
