qt-everywhere-opensource-src-x.x.x<\/code> from http:\/\/get.qt.nokia.com\/qt\/source\/<\/a>.<\/p>\nUnpack it into the directory you want the source code kept, I choose D:\\dev\\qt-src<\/code>. Create also the destination directory where you want your build to be, I chose D:\\dev\\qt-build<\/code>. The directories can be anything and they can be in different drives, but I recommend avoiding to use directory names with spaces, as this may cause problems.<\/p>\nYou will also need to have Perl installed to run the configure script of Qt. If you don’t already have it, I recommend using the portable version of Strawberry Perl for Windows. You can download it here<\/a>. As this is a one-off step and you won’t need to do this next time you want to build Qt, unpack it into a suitable location in your system. I chose D:\\dev\\perl<\/code>. Notice the batch file portableshell.bat<\/code>, as we will need this in a bit.<\/p>\n![\"Strawberry](\"https:\/\/www.npcglib.org\/~stathis\/blog\/wp-content\/uploads\/2011\/03\/strawberry-perl.png\" "\\"strawberry-perl\\"")
Directory of Strawberry Perl for Windows<\/p><\/div>\n
Configuring and Compiling Qt<\/h3>\n
Now, open the Visual Studio Command Prompt, as shown here:<\/p>\n
![\"Visual](\"https:\/\/www.npcglib.org\/~stathis\/blog\/wp-content\/uploads\/2011\/03\/vs2010-command-prompt.png\" "\\"vs2010-command-prompt\\"")
Visual Studio Command Prompt<\/p><\/div>\n
You have to open the VS Command Prompt instead of a normal Command Prompt (cmd.exe), as this will load the Visual Studio variables into your environment, e.g. location of the Visual C++ compiler, linker etc. You also have to setup your environment with Perl support, so execute from within the VS Command Prompt the portableshell.bat. You can easily do this:<\/p>\n
D:\\dev\\perl\\portableshell.bat<\/pre>\nNow that your environment is setup with both VS and Perl support, change into the directory you intend to build and run the configure script in the source directory:<\/p>\n
\r\ncd D:\\dev\\qt-build<\/font>\r\nD:\\dev\\qt-src<\/font>\\configure -ltcg -opensource -mp\r\n<\/pre>\nYou may want to have other switches for your Qt, so investigate the options with configure -help<\/code>, but these will work just fine if you don’t have any special needs. Briefly:<\/p>\n\n-
-ltcg<\/code> enables Link-time Code Generation, which tells the linker to call the compiler and perform whole program optimization.<\/li>\n-
-opensource <\/code> tells Qt you’re building for Open Source development, not commercial.<\/li>\n-
-mp <\/code> enables building Qt with multiple processes, which will speed up your build. Use this if you have a computer with multiple cores or cpus.<\/li>\n<\/ul>\nThe configure script will run for a while to compile some basic tools required and configure the Qt build for your system. Once configuration is finished you are ready to compile Qt. This may take a couple of hours and around 15-20GB of free space may be required to build everything in D:\\dev\\qt-build<\/code>. To compile the code use either the default nmake<\/code> or jom<\/a><\/code>. jom has the advantage of utilizing all cpus and cores on multicore machines and therefore it will build qt much faster than nmake. <\/p>\nSo, while still in D:\\dev\\qt-build<\/code>, to start the compilation:<\/p>\nnmake -f D:\\dev\\qt-src\\Makefile<\/pre>\nor<\/p>\n
jom -f D:\\dev\\qt-src\\Makefile<\/pre>\nOnce the compilation is finished you may also want to build the documentation for Qt Assistant, which isn’t built by default, you can do this with:<\/p>\n
nmake -f D:\\dev\\qt-src\\Makefile docs<\/pre>\njom -f D:\\dev\\qt-src\\Makefile docs<\/pre>\nIf everything goes according to plan Qt will be built in D:\\dev\\qt-build<\/code> and may occupy some 15-17GB of hard disk space. If you don’t want to rebuild Qt, you can clean up the build from intermediate files:<\/p>\nnmake -f D:\\dev\\qt-src\\Makefile clean<\/pre>\njom -f D:\\dev\\qt-src\\Makefile clean<\/pre>\nKeep in mind that you cannot delete or move<\/u> the sources from D:\\dev\\qt-src<\/code> as the shadow build files in D:\\dev\\qt-build reference headers in this directory and will not work when you try to compile software against it. If you really need to move your Qt build elsewhere then take a look at QtMove<\/a>.<\/p>\nSoftware used<\/h3>\n
(versions here are updated each time I update the toolset and libraries)<\/p>\n
\n- Microsoft Visual Studio 2010 Ultimate Edition\n
- Nokia Qt<\/a> [v4.7.2, v4.8.0, v4.8.1]\n
- Strawberry Perl for Windows (Portable)<\/a> [v5.12.1, v5.16.0]\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
A “shadow build” is an out-of-source build, where the source code is kept in one place and the build tree in another. I use this method to compile Qt on windows with Visual Studio (as of writing this post with VS2010). Preparation First download the latest Qt source code package. I usually download the latest […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[7],"tags":[9,8],"yoast_head":"\n\n\n\n\t\n\t\n\t\n