Three weeks struggling with the compilation of Qt5.1.1, I finally managed to have one built without failure message during compilation.
The main reason for previous failures, in my own opinion, is mainly due to my ignorance of one crusial factor during shadow build.
You should have your source and build folders in the same level, best in same folder.
This information has been mentioned in an old document about Qt shadow build instructions posted in nokia site before but seems cannot find it now. The current documents/wiki on qt-project site do not mention this explicitly but the example has such implied.
ZAC's Blog for sharing programming related stuffs, focus on free stuffs, occasionally will talk about paid solutions.
Translate
Showing posts with label solved. Show all posts
Showing posts with label solved. Show all posts
2013/11/22
#build #Qt5.1.1 with #mingw on #Windows finally suceeded
Labels:
build,
compile,
gcc,
MinGW,
out of source,
Qt,
Qt5.1.1,
shadow build,
solved,
Windows
2013/11/14
[#solved] #Build #Qt5.1.1 #failed again (Makefile.Debug:7091: recipe for target '.obj/debug_shared/qwindowstheme.o' failed)
Find a patch for the file qtbase\src\plugins\platforms\windows\qwindowstheme.cpp.
Need to try again.
Need to try again.
[#Solved] #Building #Qt5.1.1 static failed (Makefile:350: recipe for target 'qfilesystemengine_win.o' failed)
Finally found a patch on web to solve the issue.
You can download the patch from here.
The file to be patched is <qt-5.1.1-Folder>/qtbase\src/corelib/io/qfilesystemengine_win.cpp
Hope this time the compile can get through.
You can download the patch from here.
The file to be patched is <qt-5.1.1-Folder>/qtbase\src/corelib/io/qfilesystemengine_win.cpp
Hope this time the compile can get through.
2013/11/08
Remove the yellow ! from the kits of QtCreator's build and run environment for Qt Static build
When configuring QtCreator's Build & Run options with static Qt build, kits item will show a yellow exclamation mark due to x86-windows-unknown-pe-32bit. This seems not affecting the compilation with this static Qt build.
But if you really want to remove that yellow !, you can try to copy the Qt5Core.dll and Qt5Cored.dll from your shared build to the lib folder of your static build.
e.g.
But if you really want to remove that yellow !, you can try to copy the Qt5Core.dll and Qt5Cored.dll from your shared build to the lib folder of your static build.
e.g.
c:\Qt\5.1.1\mingw48_32 (this is installation of the Qt SDK)Then you can
c:\Qt\5.1.1\mingw48_32s (the static version)
copy /y "c:\Qt\5.1.1\mingw48_32\lib\Qt5Core.dll" "c:\Qt\5.1.1\mingw48_32s\lib\Qt5Core.dll"Source: Qt5使用静态版,在配置Build&Run环境时,kits项中会出现黄色感叹号
copy /y "c:\Qt\5.1.1\mingw48_32\lib\Qt5Cored.dll" "c:\Qt\5.1.1\mingw48_32s\lib\Qt5Cored.dll"
2013/11/05
Solving mingw-builds script download error
Using #mingw-builds to build #Qt, if encounter download error from #http://sf.net , you can download the corresponding file manually and place it inside Qt-builds/work/src/, then create an empty file with <yourDownloadFilename>.marker inside Qt-builds/work/markers/. Re-run ./buildall <yourOptions> will continue the process.
Labels:
build,
compile,
download,
error,
MinGW,
mingw-builds,
Qt,
sf.net,
solved,
sourceforge.net
Subscribe to:
Posts (Atom)