How to resolve license errors when installing the MSVC2019 Static kit
-
You'd have to buy a commercial license. However, you can use the open source version with a static build as well. The short explanation is that you'd need to distribute your object files (of your own source code) as well to conform to the LGPL, so that someone else can link to their own version of a static Qt. Note that there are also a few modules like QtCharts that are only available under the GPL or the commercial license.
@SimonSchroeder said in How to resolve license errors when installing the MSVC2019 Static kit:
However, you can use the open source version with a static build as well
What is the difference between open source and commercial versions, is the open source version the same as commercial? I saw in the qt article that if you make the application static or "static kits" it will make reverse engineering difficult, is the commercial version safer than open source?
-
@SimonSchroeder said in How to resolve license errors when installing the MSVC2019 Static kit:
However, you can use the open source version with a static build as well
What is the difference between open source and commercial versions, is the open source version the same as commercial? I saw in the qt article that if you make the application static or "static kits" it will make reverse engineering difficult, is the commercial version safer than open source?
@Blackzero said in How to resolve license errors when installing the MSVC2019 Static kit:
is the open source version the same as commercial?
Mostly. There are some modules only available as commercial.
Main difference is that with commercial license you do not have to care about open source licenses.
For more details you can ask QtCompany."qt article that if you make the application static or "static kits" it will make reverse engineering difficult" - where do you have this from. I doubt it makes it really harder.
And commercial or open source license has zero effect on reverse engineering - Qt is in both cases same... -
@Blackzero said in How to resolve license errors when installing the MSVC2019 Static kit:
is the open source version the same as commercial?
Mostly. There are some modules only available as commercial.
Main difference is that with commercial license you do not have to care about open source licenses.
For more details you can ask QtCompany."qt article that if you make the application static or "static kits" it will make reverse engineering difficult" - where do you have this from. I doubt it makes it really harder.
And commercial or open source license has zero effect on reverse engineering - Qt is in both cases same...@jsulm said in How to resolve license errors when installing the MSVC2019 Static kit:
@Blackzero said in How to resolve license errors when installing the MSVC2019 Static kit:
is the open source version the same as commercial?
Mostly. There are some modules only available as commercial.
Main difference is that with commercial license you do not have to care about open source licenses.
For more details you can ask QtCompany."qt article that if you make the application static or "static kits" it will make reverse engineering difficult" - where do you have this from. I doubt it makes it really harder.
And commercial or open source license has zero effect on reverse engineering - Qt is in both cases same...I forgot but the article mentioned, by adding Obfuscator and static kits it can make it difficult to reverse engineer, I created my own license key with layered algorithms, that's why I'm looking for ways to make it difficult to reverse engineer, I know that nothing is safe.
-
If you want to have a static build you have to also build all libraries you're using as static libs - this also includes Qt.
-
If you want to have a static build you have to also build all libraries you're using as static libs - this also includes Qt.
-
@jsulm said in How to resolve license errors when installing the MSVC2019 Static kit:
If you want to have a static build you have to also build all libraries you're using as static libs - this also includes Qt.
so I have to change my code too
-
@Blackzero
No, you do not have to change your code. You must change the way you build both your own code and Qt itself (yes, you will have to build Qt libraries) so that all of them are built/linked statically.@Blackzero I never said that. You should read about static and dynamic linking. It has nothing to do with the code of your application.
-
@Blackzero I never said that. You should read about static and dynamic linking. It has nothing to do with the code of your application.
-
@jsulm You have addressed your last post @JonB. Did you mean @Blackzero, the OP? :)
@JonB said in How to resolve license errors when installing the MSVC2019 Static kit:
Did you mean @Blackzero, the OP?
Yes, I did. Sorry :-)
-
@jsulm said in How to resolve license errors when installing the MSVC2019 Static kit:
@Blackzero said in How to resolve license errors when installing the MSVC2019 Static kit:
is the open source version the same as commercial?
Mostly. There are some modules only available as commercial.
Main difference is that with commercial license you do not have to care about open source licenses.
For more details you can ask QtCompany."qt article that if you make the application static or "static kits" it will make reverse engineering difficult" - where do you have this from. I doubt it makes it really harder.
And commercial or open source license has zero effect on reverse engineering - Qt is in both cases same...I forgot but the article mentioned, by adding Obfuscator and static kits it can make it difficult to reverse engineer, I created my own license key with layered algorithms, that's why I'm looking for ways to make it difficult to reverse engineer, I know that nothing is safe.
@Blackzero said in How to resolve license errors when installing the MSVC2019 Static kit:
I forgot but the article mentioned, by adding Obfuscator and static kits it can make it difficult to reverse engineer, I created my own license key with layered algorithms, that's why I'm looking for ways to make it difficult to reverse engineer, I know that nothing is safe.
If you are using static linking you can strip all symbols from your program. However, I doubt that this is possible under the LGPL. If you really want to use this approach, you need to buy a commercial Qt license.
