@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

No issue in using it.

The only thing to take into account is that any update to the Qt provided xcb library won't happen until next release of Qt (unless you're building from the latest git revision) while your system xcb will follow your distribution updates.

That's a tradeoff that only you can decide upon.

@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).

Thanks. I take a look at hat and at http://tishion.github.io/QCefView/

But then we end up in using an extra lib. Something we want to avoid.... :-(

Hi and welcome to devnet,

If you want a full static application then you have to also build all dependencies as static and since you're on Windows, you also have to take into account the Visual Studio Runtime (since you are using a Visual Studio Qt build). Note that this is nothing Qt specific.

No, you don't have to delete anything, you can use several builds of Qt in parallel without any problem. How fast your build time will be depends on the machine you have.

Developing applications and the type of builds are two completely unrelated topics.

Note that using a static build of Qt has licensing implications.

Okay... finally i solved it. Nothing to do with .pro file or PLUGIN macro. It was a basic PATH issue. qmake was searching for 'plugin' directory in /PREFIX path not in /SYSROOT/PREFIX path. I just copied all plugin directory from /SYSROOT/PREFIX to /PREFIX directory. I know this may not be the right way, but it temporarily solved my issue. If someone could suggest the correct solution please let me know.

Thatt did the trick, thanks!

As long as you abide by the GPL, you're good.

You have a list of examples here

use macro:
Q_IMPORT_PLUGIN(QLinuxFbIntegrationPlugin);

I updated a .pro file to the following state:

QT += core multimedia widgets
QT -= gui
TARGET = MetadataExtractor
CONFIG += console
CONFIG += static
TEMPLATE = app
SOURCES += main.cpp
extractor.cpp
HEADERS +=
extractor.h

Then used the macdeployqt. This issue is resolved for me.
@SGaist @Tyras @kshegunov Thanks to Everyone!

@Konstantin-Tokarev yes it is, i was thinking of trying an older version of ruby as i just grabbed the newest one..

Having a static Qt doesn't mean that all dependencies are gone. Qt might be static but unless you also link to the static version of all its dependencies, what you have is normal: OpenGL and the xcb plugin deps.

Use this. My Problem was solved by following that mentioned steps. Before you start, read the comments below.

Does anyone have instructions for Qt static build that is version 5.4 or greater?

@Skeffington
Cheers :)

The XXX was meant to be replaced with whatever sql plugin you wanted to have built-in

Since you have it working now, please update the thread title prepending [solved] so other forum users may know a solution has been found :)

Finally I'm able to automatically copy the qt translation files and create resource file from the pro file:

TRANSLATIONS = myapp_cs.ts \ myapp_xx.ts QT_TRANSLATIONS = qtbase_cs.qm #------------------------------------------------- # create lang folder QM_DIR = $$shadowed($${PWD})/lang mkpath($${QM_DIR}) mkpath($${QM_DIR}/lang) #------------------------------------------------- # copy system translation files to lang folder for(FILE,QT_TRANSLATIONS){ FILE = $$shell_path($$[QT_INSTALL_TRANSLATIONS]/$${FILE}) system($${QMAKE_COPY} $${FILE} $$shell_path($${QM_DIR}/lang)) } #------------------------------------------------- #generate qm files directly from qmake for(FILE,TRANSLATIONS){ QM_FILE = $$shell_path($${QM_DIR}/lang/$$replace(FILE,.ts,.qm)) system(lrelease $${FILE} -qm $${QM_FILE}) } #------------------------------------------------- #create resource file with translations win32:system(cd $$shell_path($${QM_DIR}) & rcc --project -o lang.qrc) unix:system(cd $$shell_path($${QM_DIR}) ; rcc --project -o lang.qrc) RESOURCES += $${QM_DIR}/lang.qrc #------------------------------------------------- # extra target to generate ts translation files lupdate.commands = lupdate $$_PRO_FILE_ lupdate.depends = FORCE QMAKE_EXTRA_TARGETS += lupdate #------------------------------------------------- # extra compiler to generate qm translation files lrelease.input = TRANSLATIONS lrelease.output = $${QM_DIR}/lang/${QMAKE_FILE_BASE}.qm lrelease.commands = lrelease ${QMAKE_FILE_NAME} -qm ${QMAKE_FILE_OUT} lrelease.CONFIG += no_link target_predeps QMAKE_EXTRA_COMPILERS += lrelease

Another interesting development: I tried running on another machine with the Qt toolchain installed, and the program worked. So it appears it is still reading something from the filesystem that is not on a regular Windows machine, but I don't know what that might be. I did package all the qmldir files needed for Qt Quick to work.

I have a similar issue as well.

some error while compiling.

although instead of undefined reference to i am getting something like deprecated function. No idea whats the problem.

Thanks

Scot V
Development Team
Fastest Web Browser

@jitu059_Lalat The long and short if it are, you have two ways to do this:

Find all the dll's that your app depends on. You can do this with the tool http://www.dependencywalker.com/. Once you found all the dll's copy them into the same folder as your executable. This is now your "delivery package" you will copy the executable + dlls from PC to PC. This method is perhaps a bit easier/faster in the short term, but when you compile with different versions of Qt/Windows you may require a different set of dlls (i.e. Qt4 Dlls don't match Qt5 Dlls).

Download the Qt source code and compile it for static linking. Then when you build your code you will get a much larger executable file, but it will contain everything it needs - a standalone executable. This is perhaps a bit more work on your part, but master this and it makes deploying your project from PC to PC much easier.

Have a go at one or other method, if you get stuck then ask again. But as SGaist said, there is lots of documentation out there already : )

I can confirm similar issue on Mac OS X 10.11.3.
But successful build was with with flags:
-nomake examples -nomake tests

Waiting online~~~

On it. Merci!