Build exe-file of Qt4-Project
-
These are the finales lines that just state the compilation failed. Above these are those that are containing what is currently failing to build.
-
@SGaist said in Build exe-file of Qt4-Project:
These are the finales lines that just state the compilation failed. Above these are those that are containing what is currently failing to build.
There is something like this:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.12.25827\include\cstdint(46): error C2039: "uintmax_t": Ist kein Element von "`global namespace'"
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.12.25827\include\cstdint(46): error C2873: "uintmax_t": Das Symbol kann nicht in einer using-Deklaration verwendet werden -
Ok... I didn't realised that you where using VS2017. The latest version of Visual Studio used to build Qt 4.8 was 2015. You will have to copy the 2015 mkspec and tweak it in order to build it.
MinGW might be a quicker choice depending on your needs.
-
@SGaist said in Build exe-file of Qt4-Project:
Ok... I didn't realised that you where using VS2017. The latest version of Visual Studio used to build Qt 4.8 was 2015. You will have to copy the 2015 mkspec and tweak it in order to build it.
MinGW might be a quicker choice depending on your needs.
I will try to build it with Visual Studio 2015 tomorrow. Thanks for your hint.
-
During which part of the build ?
-
So configure is successful ?
-
By the way, which version of 4.8 is it ?
-
Did you check which mkspec gets selected when configuring Qt ?
-
I also tried it that way:
https://wiki.qt.io/How_to_build_a_static_Qt_version_for_Windows_with_gcc
But at the step where to modify the file qtenv.bat I don't find such a file in my Qt-folder.
-
@SGaist said in Build exe-file of Qt4-Project:
This one looks more recent.
This one also doesn't work.
I tried now the tool windeployqt which comes with Qt5, but it seems to work only with Qt5-binaries. It would be enough if I could pack the exe file of my project with the necessary dlls in one folder so it runs on every Windows computer.
-
Then use Dependency Walker to get the dll used by your application and add the necessary plugin if any is needed and you should be good to go.
-
What do you mean by doesn't work ?