2013

12/07/2015 stathis 9 comments

I just finished compiling and packaging my Qt 5.5.0 set of builds. You can download the new builds in the Precompiled Qt4 and Qt5 section. These builds are for both the 32- and 64-bit Windows and they are particularly useful if one wants to build static binaries. However, please be aware that there are serious licensing issues in using static linking and therefore you should investigate by yourself.

If you have issues do email me or leave a comment, but note that the builds are experimental and are only here just for my personal backup and use. Many thanks to the Qt developers and contributors!

enjoy :-)

windows precompiled libraries, Qt, Qt5, static compilation, visual c++, visual studio

#1 | Written by Vlad about 8 years ago. Reply

Thank you a lot for your work. Would you please provide configuration options for the qt 5.5.0 vs2013 x86? I use qsqlodbc.dll in my project. Would you please help me with this particular library? How can I build qsqlodbc.dll/lib using your compiling and packaging sets?

0
- #2 | Written by stathis about 8 years ago. Reply
  
  There is no qt compilation scripts yet. Maybe it will be better if you ask on the Qt Forums. I generally don’t have as much time as I would have liked to help individuals like you out.
  
  0
#3 | Written by malek about 9 years ago. Reply

The ICU 55.1 build seems to be fixed now (at least for msvc2010).

Qt creator can now generate x86 static /MT release msvc 2010 exes that can run standalone in a vanilla windows xp.

Qt Quick apps compile and build correctly, but start with a blank window, and the following message on the console: module “QtQuick” is not installed

0
- #4 | Written by stathis about 9 years ago. Reply
  
  malek, do you think you can provide me a minimal example that I can try compile (on my email ideally: stathis@npcglib.org)? I don’t use Qt Quick, so it is not clear to me what may be the problem. Willing to investigate though. Could it be related: http://www.qtcentre.org/threads/60907-How-to-distribute-a-qt-quick-application-to-a-computer-without-QT-installed
  
  0
#5 | Written by Simha about 9 years ago. Reply

Shall you explaing what is static binaries and shared binaries. I really confused about this.

0
- #6 | Written by stathis about 9 years ago. Reply
  
  They’re shorthand for statically linked binaries of a library or dynamically linked binaries of a library.
  I think this here explains it in a simple way that is easy to follow: http://stackoverflow.com/questions/2649334/difference-between-static-and-shared-libraries
  
  0
#7 | Written by malek about 9 years ago. Reply

Thanks a lot for creating this builds !!
As someone who tried to produce static builds of Qt, I know the pain.

I just downloaded the Qt MSVC2010 build in order to only use the x86 static release build.
I also downloaded your ICU v55.1 and OpenSSL v1.0.2d builds.
I’m using a freshly installed and updated Visual C++ Express 2010
This is what I concluded:
– Setting up the new build in Qt Creator was straighforward …
– Testing an example project, the compilation went fine using the default settings (cl -c -nologo -Zc:wchar_t -O2 -MT -GR -W3 -w34100 -w34189 -w44996 -EHsc -DUNICODE -DWIN32 -DQT_NO_DEBUG -DQT_QUICK_LIB -DQT_GUI_LIB -DQT_QML_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DNDEBUG ….)

– 1st Error when linking: fatal error LNK1104: cannot open file ‘D:\dev\openssl\openssl-1.0.2d-vs2010\lib\libeay32MT.lib
(This was corrected by changing every instance of “D:\\dev\\openssl\\openssl-1.0.2d-vs2010\\lib\\” -> “$$[QT_INSTALL_LIBS]\\” in all prl files and copying libeay32MT.lib and ssleay32MT.lib to qt5.5-msvc2010-static-x86’s lib folder)

– The same was done for “D:\\dev\\icu\\icu-55.1-vs2010\\lib\\”, and all release sicu*.lib files were copied to the same previous folder.

– Linking started to get going again, but quickly failed with 17 errors of this kind:
Qt5Core.lib(qlocale_icu.obj) : error LNK2019: unresolved external symbol _u_strToUpper_55 referenced in function “class QString __cdecl QIcu::toUpper(class QByteArray const &,class QString const &,bool *)” (?toUpper@QIcu@@YA?AVQString@@ABVQByteArray@@ABV2@PA_N@Z)

All Errors involved Qt5Core.lib and an unresolved external symbol that ends with _55.
(_u_strToUpper_55 _u_strToLower_55 _ucnv_close_55 _ucnv_compareNames_55 _u_errorName_55 _ucnv_setSubstChars_55 _ucnv_open_55 _ucnv_toUnicode_55 _ucnv_fromUnicode_55 _ucnv_getMaxCharSize_55 _ucnv_getAlias_55 _ucnv_countAliases_55 _ucnv_getStandardName_55 _ucnv_getAvailableName_55 _ucnv_countAvailable_55 _ucnv_getDefaultName_55) to be precise :D

After examining a few lib files with dumpbin, a found a reference for _u_strToUpper_54 (and not _u_strToUpper_55) in sicuuc.lib (correctly linked), sicuio.lib and sicuin.lib (linked later for the sake of testing)

I examined other static libraries from ICU v55.1 and ICU v54.1(built by msvc2010, 2012 and 2013), and it was always _u_strToUpper_54 that is exported.

Also, Qt5Core.lib from Qt5 v5.4.2 MSVC2010 x86 static release import _u_strToUpper_55 (and various other _55 functions)

Please let me know what do you think.
And thanks again for your work.

0
- #8 | Written by stathis about 9 years ago. Reply
  
  Firstly, thanks for the heads up on the .prl, I was actually looking exactly at this last night and I figured out that make install of Qt5 isn’t modifying the .prl files to include that, but hard codes the path in the build. I will see if I can do anything at config time or wordaround it, alternatively I will file a feature request with Qt. I think there is a problem with the ICU 55.1. I recently rebuild 55.1 to include MSVC2008, but from quick inspection after your post, I think the 55.1 releases are all wrong now. It seems on my second rebuild ICU 54.1 source code was fetched despite the naming. I will rebuild everything, but I need to recheck. Thanks a lot, give me some time.
  
  0
- #9 | Written by raku about 9 years ago. Reply
  
  Thanx, with this changes it works!
  
  0

sigmoid

Qt 5.5.0 for MSVC 2010/2012/2013

Leave a Comment