I want to know open source protocols for some dlls.
-
The QT version I am using is 5.12.8,. What open source protocols do I need to follow when using some DLLs, such as libwinpthread-1.dll, libstd c++-6.1dll, libssl-1_1. dll, Opengl32sw. dll, Opengl32sw. dll, libiconv-2. dll, libgcc_s_dw2.dll, libEGL.dll, libcrypto-1.dll? Is it LGPL?
-
What do you mean with 'protocols'? These are dlls so you normally access them with c/c++, not with any 'protocol'.
-
I am engaged in commercial software development and would like to know which open source projects these DLLs belong to? What open source protocols should be followed?
-
The QT version I am using is 5.12.8,. What open source protocols do I need to follow when using some DLLs, such as libwinpthread-1.dll, libstd c++-6.1dll, libssl-1_1. dll, Opengl32sw. dll, Opengl32sw. dll, libiconv-2. dll, libgcc_s_dw2.dll, libEGL.dll, libcrypto-1.dll? Is it LGPL?
@tony123456
Something like (I don't guarantee 100% accuracy):- libwinpthread-1.dll, libstd c++-6.1dll, libiconv-2. dll, libgcc_s_dw2.dll : MinGW/gcc compiler/linker libraries
- libssl-1_1. dll, libcrypto-1.dll : OpenSSL
- Opengl32sw. dll, Opengl32sw. dll, libEGL.dll : handles OpenGL calls
I would assume/guess all of these are open source, whether that be LGPL or some other license. I do not believe using any of them would impose any restrictions on your code or obligations to end users.
Still don't know what "open source protocols should be followed" might mean.
Note that I am not lawyer, if you need to verify my statements or know more about these you should do your own investigations.
-
Thank you very much！
-
@tony123456
Something like (I don't guarantee 100% accuracy):- libwinpthread-1.dll, libstd c++-6.1dll, libiconv-2. dll, libgcc_s_dw2.dll : MinGW/gcc compiler/linker libraries
- libssl-1_1. dll, libcrypto-1.dll : OpenSSL
- Opengl32sw. dll, Opengl32sw. dll, libEGL.dll : handles OpenGL calls
I would assume/guess all of these are open source, whether that be LGPL or some other license. I do not believe using any of them would impose any restrictions on your code or obligations to end users.
Still don't know what "open source protocols should be followed" might mean.
Note that I am not lawyer, if you need to verify my statements or know more about these you should do your own investigations.
@JonB said in I want to know open source protocols for some dlls.:
Still don't know what "open source protocols should be followed" might mean.
I guess OP was asking if there are any steps required or any procedure he has to follow when using these kind of libs in this commercial project.
@tony123456
So, yeah, also not a lawyer, but since they are DLLs and dynamically linked, you can use LGPL stuff in your commercial app.
AFAIK not allowed is to statically link LGPL covered code into your commercial app or main product.
If debugging is the process of removing software bugs, then programming must be the process of putting them in.
~E. W. Dijkstra
-
@JonB said in I want to know open source protocols for some dlls.:
Still don't know what "open source protocols should be followed" might mean.
I guess OP was asking if there are any steps required or any procedure he has to follow when using these kind of libs in this commercial project.
@tony123456
So, yeah, also not a lawyer, but since they are DLLs and dynamically linked, you can use LGPL stuff in your commercial app.
AFAIK not allowed is to statically link LGPL covered code into your commercial app or main product.@Pl45m4 said in I want to know open source protocols for some dlls.:
AFAIK not allowed is to statically link LGPL covered code into your commercial app or main product.
Don't really want to revisit this but that is not so. For one thing if that were true it would preclude Qt (LGPL parts, no GPL parts) being linked statically without paying for commercial, and that is not the case.
-
@Pl45m4 said in I want to know open source protocols for some dlls.:
AFAIK not allowed is to statically link LGPL covered code into your commercial app or main product.
Don't really want to revisit this but that is not so. For one thing if that were true it would preclude Qt (LGPL parts, no GPL parts) being linked statically without paying for commercial, and that is not the case.
@JonB said in I want to know open source protocols for some dlls.:
For one thing if that were true it would preclude Qt (LGPL parts, no GPL parts) being linked statically without paying for commercial, and that is not the case.
This is what happens when you're half-sleep while doing research :D
Apparently this seems to be true for LGPL 2 and older (haven't checked that in detail)Thanks for the clarification. ;-)
-
Hi,
You essentially have to abide by the licensing rules. For example, some, such as the LGPL, require that you have an easy to find place which lists the dependencies and the corresponding license such as an about box. Or, still for the LGPL, your user shall be able to switch out the libraries bundled with their own. This implies that if you are using a static build, you have to provide the build artifacts necessary to recreate the binary.
Also, since you might be using OpenSSL, some countries have restrictions with regard to software using cryptography.
-
Qt has a list of third-party libraries used together with their licenses: https://doc.qt.io/qt-6/licenses-used-in-qt.html
