Hi,

That part comes from KDE, I would recommend also checking with them.

You can use the QTC_STATIC_BUILD CMake variable set to ON to build Qt Creator statically.

For optimal performance you also need to set CMAKE_INTERPROCEDURAL_OPTIMIZATION to ON.

Thanks,
I am distributing my source code via GitHub and GPL. I think that so long as I do that, it doesn't matter whether or not I use static linking in so far as licensing is concerned. My code is open-source, at least that's my intent.

I did find that I was able to easily modify the makefile emitted by Qt Creator to force static linking of most, but not all of the Linux system dependencies. Apparently, some of the OS libraries were available only as shared libraries and in some cases Qt libraries called shared Linux OS libraries so that I was not able to use all the available static libraries offered by Linux.

Too bad that it doesn't appear that one can roll up a desktop app all into one executable with no shared library calls. I'm thinking this would be nice since then, it could be distributed to any Linux machine without consideration of the distribution or kernel version?

Thanks,
Phil

I searched for this problem a lot and found the problem in the link below, which is related to a bug in version Qt5.14.0 that has been fixed in higher versions.
I tested with version Qt5.14.2 and it was compiled without error.
https://stackoverflow.com/questions/41765673/static-linking-against-qt-on-windows-using-cmake

https://codereview.qt-project.org/c/qt/qtbase/+/282408

i am facing the same nightmare. it's 2weeks i'm stuck tryin' to obtain my static +openssl build and...no way.

No issues compiling without openssl support.

Any progress on that? Seems that nobody wants to help :(

Hi,

Since you have a commercial licence, I would recommend opening an issue directly from your account as you have access to support.

@sierdzio Thank you. Will look into it.

@EinderJam said in "Mismatch detected for RuntimeLibrary" when trying to statically compile with a static build of Qt:

Before building, using this tutorial, I modified qt-everywhere-src-5.11.1\qtbase\mkspecs\msvc-desktop.conf and replaced every -MD by -MT
Build process went fine.

If you changed the Qt compilation flags at some point, did you clean out absolutely everything before rebuilding? Many times it seems bits get left over which have been compiled with previous flags.

@ed-wright

Not sure, but probably you have to do a "nmake distclean" in between or it finds your license information. However, this is the opensource forum. You would need to approach the commercial, they have to able to give the proper answer.

Super good work.
Thanks for updating on the way. will be helpful for others.

Hi,

Use the amd64 command prompt when building Qt.

Hi and welcome to devnet,

Do you have any static QWidget based class in your library/application ?

I made several modifications ... but i think the properly modifications are

In : QtSrc\qtbase\mkspecs\win32-g++\qmake.conf add

QMAKE_LFLAGS += -static -static-libgcc QMAKE_CFLAGS_RELEASE -= -O2 QMAKE_CFLAGS_RELEASE += -Os -momit-leaf-frame-pointer DEFINES += QT_STATIC_BUILD

In : QtSrc\qtbase\src\plugins\sqldrivers\oci\oci.pro add

QMAKE_LFLAGS += oracle_home\oci\lib\msvc\oci.lib QMAKE_LFLAGS += oracle_home\oci\lib\msvc\ociw32.lib QMAKE_LFLAGS += oracle_home\oci\lib\msvc\oraocci11.lib LIBS += -Loracle_home\oci\lib\msvc -loci -lociw32 -loraocci11 INCLUDEPATH += oracle_home\oci\include

cmd

-static -debug-and-release -platform win32-g++ -prefix QtPath\Static -I C:\\OpenSSL-Win32\\include -L C:\\OpenSSL-Win32\\lib -opensource -confirm-license -c++std c++14 -nomake examples -skip qtdoc -skip wayland -skip purchasing -skip serialbus -skip qtserialport -skip script -skip scxml -skip speech -skip location -no-opengl -no-angle -qt-zlib -qt-pcre -qt-libpng -no-libjpeg -qt-freetype -sql-oci -I oracle_home\oci\include -L oracle_home\oci\lib\msvc

try it. the other modifications do not matter

I'm no expert but as far as i know, there is static and static. First static is static Qt-Libs second static is a real static standalone executable file.

If you want a real standalone executable you have to get a static version of all dependencies ".a" files not ".so". And you have to add some magic to the compiler -static -static-libgcc -static-libstdc++ (add in the Qt source to qtbase/mkspecs/linux-g++/qmake.conf) and if you want to use any kind of networking, you may also need static nss https://github.com/nss-dev/nss (some Linux versions still got static nss avaliable over packed managers).

And even if you don't use networking in your app, some other libs may include networking even if you don't use it in your code directly.

Good luck! :)

@jordanbaucke Sure, since you have commercial license you can bring the point directly to support.

You could certainly make use of UPX, it should get the filesize down to maybe 4MB (by using compression).