I wanted to migrate my Qt 4 app to use Qt 5 instead. These instructions failed, due to some differences with how MXE builds Qt 5, including the fact that it uses modularised Qt tarballs, instead of one large tarball.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Here are the full instructions:
Get it:
Install build dependencies
Build Qt 5 for Windows:
This will first build its dependencies and the cross-build tools;
It should take less than an hour on a fast machine with decent internet access.
Due to the new modular nature of Qt 5, various major Qt components are now in different tarballs. The one selected above,
qtbase, should give you enough functionality to run ordinary GUI apps, which is all I needed for my own (smallish) app.If you want to build all of Qt 5 instead, you’ll need to run
make qt5(instead ofmake qtbase). Note that it will take a lot longer to complete, so be sure that you need the extra functionality.Get to the directory of your app, and run the Qt Makefile generator tool:
Build your project:
You should find the binary in the ./release directory:
Some notes:
This was tested on my 64-bit Debian 8, and on Windows of course.
The output is a 32-bit static executable, which will work well on 64-bit Windows.
If you want a 64-bit executable, build Qt with:
The default
MXE_TARGETSvalue isi686-w64-mingw32.static.