Qt for Web Assembly and the Open Source version
-
Hello, I am new to Qt (and web assembly) and trying to figure out how licensing works. I am writing a piece of software for a client intended for internal use but, being 18 years old, I cannot afford the $500 small business license and am trying to remain in line with the Open Source version of the Qt framework.
With the other platforms, it seems I can just avoid using certain components and keep dynamic linking enabled as to not violate the LGPL v3 license, but with web assembly, this seems like more of a predicament, as you cannot allow the user to freely change the .dll of the LGPL v3 licensed components.
Because I'm being contracted to write this software for the in-house use of a single organization, I'm not sure how that fits into the "personal use" conditions of the licenses.
If anyone could help me navigate this, I'm putting as much concern into this as I am the actual project despite probably having no risk of being sued. -
Hello, I am new to Qt (and web assembly) and trying to figure out how licensing works. I am writing a piece of software for a client intended for internal use but, being 18 years old, I cannot afford the $500 small business license and am trying to remain in line with the Open Source version of the Qt framework.
With the other platforms, it seems I can just avoid using certain components and keep dynamic linking enabled as to not violate the LGPL v3 license, but with web assembly, this seems like more of a predicament, as you cannot allow the user to freely change the .dll of the LGPL v3 licensed components.
Because I'm being contracted to write this software for the in-house use of a single organization, I'm not sure how that fits into the "personal use" conditions of the licenses.
If anyone could help me navigate this, I'm putting as much concern into this as I am the actual project despite probably having no risk of being sued.Hi, and welcome!
@iSchraeder said in Qt for Web Assembly and the Open Source version:
Because I'm being contracted to write this software for the in-house use of a single organization, I'm not sure how that fits into the "personal use" conditions of the licenses.
Since you are writing this for someone else, it does not count as "personal use". It is personal use only if you yourself are the end-user of the software.
With the other platforms, it seems I can just avoid using certain components and keep dynamic linking enabled as to not violate the LGPL v3 license, but with web assembly, this seems like more of a predicament, as you cannot allow the user to freely change the .dll of the LGPL v3 licensed components.
That's correct. You either purchase a commercial license, or you use Qt WebAssembly under the GPLv3 license.
If you go with the GPLv3 license, then you must provide your client with a full copy of your source code, the license text, as well as a written offer to provide them with the source code of Qt. However, since your client is intending it for internal use, they don't need to provide the code or the application to anyone else.
(Under the GPLv3, the code only needs to be offered to whoever receives the software)
If anyone could help me navigate this, I'm putting as much concern into this as I am the actual project despite probably having no risk of being sued.
We're happy to help where we can. Just note that what I wrote above is based on my personal understanding, is not comprehensive, and does not constitute legal advice.
