.CuteBuilder consists in a wizard which automatically detects the available compilers and configures the build environment to compile Qt with the selected one. It also offers exclusive compiler options which are normally only available to people who have a strong knowledge of both the Qt build system and the Visual C++ compiler.
For example, it is possible to compile a special version of Qt which better exploits the optimizating capabilities of Visual C++ (Whole Program Optimisation / Link-time Code Generation), or to obtain standalone binaries which require no dll installation on the target machine (like msvcr80.dll / msvcp80.dll or msvcr90.dll / msvcp90.dll), which also allows better optimization as there is no DLL boundary.
It also allows you to select wich parts and libraries to compile, wich helps to dramatically reduce the total build time.
Ratings & Comments
5 Comments
Hello please add this "compile Qt in both debug and release" Thanks
This would be a great tool if it was possible to compile Qt in both debug and release. This is currently not possible. Why not? :) It's rather useless as it is now. This is using Qt 4.5.1 on Vista. First: CuteBuilder does all the magic in one mode only (debug or release). Should be possible to choose both configurations at the same time? Otherwise: thanks for your effort.
I'm trying out your tool, wanting to build the commercial version of Qt 4.4.3. When I click "next" (after specifying the path to my source) I receive an error titled "Wrong directory", stating "Unable to get the license of this version of Qt.Please make sure you entered a correct path to the Qt source code you want to compile. What leads to this error? If I copy a file (or more) from an open source Qt path, I can convince CuteBuilder to run against my commercial source, or will there be other issues?
Ok, using Process Monitor I was able to trace what you're doing. I copied License.GPL2 from an open source version and was able to get past this issue. You might choose to add a search for ".LICENSE-DESKTOP", ".LICENSE-ALLOS", and perhaps ".LICENSE-EVALUATION" before failing. (SIC; all of those begin with a . )
Thank you for your feedbacks, and sorry that I missed your comments. I suspected something was wrong with commercial licenses, but because I do not own such a license I can not test... I will take note of your recommendations in the next release ;)