Qt in One DLL at Release
-
Dear Community,
how about making Release and Deployment easier by Creating a single DLL Qt.dll when someone compiles it on Release Mode?
It were still LGPL since everyone could compile it too.
I don't mean to fuse all DLLs (even not needed in the Project) into one DLL. I mean only fuse the DLLs needed.
Greetings
-
Dear Community,
how about making Release and Deployment easier by Creating a single DLL Qt.dll when someone compiles it on Release Mode?
It were still LGPL since everyone could compile it too.
I don't mean to fuse all DLLs (even not needed in the Project) into one DLL. I mean only fuse the DLLs needed.
Greetings
-
What is the benefit of such configuration? Unlike static build, you still need to copy that DLL, however right now windeployqt will copy all DLLs as a single command. Also, such configuration makes debugging harder
-
What is the benefit of such configuration? Unlike static build, you still need to copy that DLL, however right now windeployqt will copy all DLLs as a single command. Also, such configuration makes debugging harder
-
Advantages:
Only 1 QT DLL is deployed.
you have better overview in your folder@seppyqt said in Qt in One DLL at Release:
Advantages:
Only 1 QT DLL is deployed.
you have better overview in your folderWhy not make a static build?
Advantages:
No Qt DLL is deployed.
you have better overview in your folderQt Doc Search for browsers: forum.qt.io/topic/35616/web-browser-extension-for-improved-doc-searches
-
@seppyqt said in Qt in One DLL at Release:
Advantages:
Only 1 QT DLL is deployed.
you have better overview in your folderWhy not make a static build?
Advantages:
No Qt DLL is deployed.
you have better overview in your folder@jksh said in Qt in One DLL at Release:
@seppyqt said in Qt in One DLL at Release:
Advantages:
Only 1 QT DLL is deployed.
you have better overview in your folderWhy not make a static build?
Advantages:
No Qt DLL is deployed.
you have better overview in your folderDon't forget to take into account the license constraints that comes with the use of a static build.
-
And further to what @SGaist has just said about licensing required for static, I would have thought you would probably run the same risk with your "all Qt DLLs into one DLL". The LGPL requires users should be able to just use a new set of Qt DLLs with your software, recompile Qt for themselves etc., and that might not hold (in a straightforward fashion) if you start replacing the standard, freely available Qt DLLs with some concoction you create yourself.
