Building Qt Desktop for Windows with MSVC

From Qt Wiki
Jump to: navigation, search
This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine.
Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean.


Building Qt Desktop for Windows with MSVC

Required SDKs and tools

Here are the tools required to build a Qt Shared or a Qt Static library. First, please, download and install :

1. Qt source code (I think you know where to find it :))
2. On machines not having a previous Qt version already installed you need to install also Perl (e.g. ActivePerl ) prior to configure. Otherwise you may receive following error message at the end of configure:
> Perl not found in environment - cannot run syncqt.
3. Microsoft Platform SDK (most recent at time of last wiki edit is Microsoft Windows 7.1 SDK.). The SDK includes the Microsoft Visual C++ compilers and debugging tools. You can in addition install Visual Studio Express if you like the IDE (not required!).
4. KB2485545 or Service Pack 1 are required for MSVC 2010 when building a 64bit library on intel x86 based CPUs. They fix a bug in the MSVC2010 compiler, and without it you will experience crashes when running 64bit binaries.
5. OpenSSL libraries or source code (if you want to build it yourself)

For Shared (if you want Phonon support) also required

  1. Microsoft DirectX SDK

Ok, all done but… If you decided to build OpenSSL yourself (really, I recommend you) it is also required

  1. ActivePerl (community edition is free)
  2. The Netwide Assembler

Installation

At first I recommend you to install all packages into one directory (for example _C:):

  • C: (for Visual C+)
  • C:7.1 SDK (for platform SDK)
  • C: (for OpenSSL library or unpack source code anywhere for build)

It is not required to install examples, demos, docs, libraries not for target architecture e.g. ;)

Environment setup

It looks good to have a script to set up the environment instead of setting it all using system PATH variable:

@ECHO OFF
 
set DEV=C:set QTDIR=%DEV%set PATH=%SystemRoot%;%SystemRoot%32;%QTDIR%
 
echo Setting OpenSSL Env.
set OPENSSL=%DEV%set PATH=%OPENSSL%;%PATH%
set LIB=%OPENSSL%set INCLUDE=%OPENSSL%
 
echo Setting NASM Env.
set PATH=%DEV%;%PATH%
 
echo Setting DirectX Env.
set LIB=%DEV%SDK\Lib\x86;%LIB%
set INCLUDE=%DEV%SDK\Include;%INCLUDE%
 
echo Setting Windows SDK Env.
set WindowsSdkDir=%DEV%7.1 SDK
set PATH=%WindowsSdkDir%;%PATH%
set LIB=%WindowsSdkDir%;%LIB%
set INCLUDE=%WindowsSdkDir%;%INCLUDE%
set TARGET_CPU=x86
 
echo Setting MSVC2010 Env.
set VSINSTALLDIR=%DEV%set VCINSTALLDIR=%DEV%set DevEnvDir=%VSINSTALLDIR%7\IDE
set PATH=%VCINSTALLDIR%;%VSINSTALLDIR%7\Tools;%VSINSTALLDIR%7\IDE;%VCINSTALLDIR%;%PATH%
set INCLUDE=%VCINSTALLDIR%;%INCLUDE%
set LIB=%VCINSTALLDIR%;%LIB%
set LIBPATH=%VCINSTALLDIR%
 
echo Setting Framework Env.
set FrameworkVersion=v4.0.30319
set Framework35Version=v3.5
set FrameworkDir=%SystemRoot%.NET\Framework
set LIBPATH=%FrameworkDir%amp;#37;FrameworkVersion%;%FrameworkDir%amp;#37;Framework35Version%;%LIBPATH%
set PATH=%LIBPATH%;%PATH%
 
echo Env. ready.
 
title Qt Framework 4.7.1 Development Kit.
 
cd %DEV%

This file is .bat (or.cmd) script. Just modify and save it for your environment. I set it up from tool’s (MSVC, SDKs) prompts.

You can add it to start menu or make a label (change script address at label preferences to "cmd /k path/to/setqtenv.cmd").

What we have

C:\Development

At my computer I have installed MSVC+ 2010 Express Edition to C:, Windows 7.1 SDK C:7.1 SDK, DirectX SDK C:SDK, Perl C: (impossible to change), NASM unpacked to C:, Qt Desktop (4.7.1) source code (from qt-everywhere-opensource-src-4.7.1.tar.gz) unpacked to C: and OpenSSL source code unpacked to C:–1.0.0c

"Static" tips

Before you start to build a static Qt Desktop library, you must know that for now you will have a dependence with MSVC Redistributable. To escape this you must replace -MD (d) build flag with -MT (d) (I will not recommend you use it, because it can cause runtime errors, etc. For example with this configuration I cannot start QtDesigner app. The reason is unknown.)

It's available as both Static and Shared builds.

Building OpenSSL

At first, open your new Qt prompt, cd to your OpennSSL source directory and setup (if not set) Perl bin directory path (and check it?):

> cd openssl-*
> set PATH=C:;%PATH%
> echo %PATH%

Something like this:

OpenSSL build setup

If all is ok, we can continue…

Configuring and preparing OpenSSL (copy-paste it, here is underscore symbols):

If you have NASM:

> perl Configure VC-WIN32 —prefix=C:> ms\do_nasm

And if not:

> perl Configure VC-WIN32 no-asm —prefix=C:> ms\do_ms

Here we set up compiler and destination directory.

Now open ms\ntdll.mak (for Static — ms\nt.mak) file and replace at LFLAGS /debug with /release.

For Static build flag -MT is applied by default (look at "Static" tips). For shared -MD is used (change CFLAG’s at ms\ntdll.mak from /MD to /MT if required for you).

Ok, building, testing and "installing":

For Shared:

> nmake -f ms\ntdll.mak
> nmake -f ms\ntdll.mak test
> nmake -f ms\ntdll.mak install

And for Static:

> nmake -f ms\nt.mak
> nmake -f ms\nt.mak test
> nmake -f ms\nt.mak install

Ready. Now you can remove your OpenSSL source code (C:–1.0.0c here, on screenshot) directory and Perl installation. They are no longer required.

Configuring Qt Desktop

There are 2 steps:

  1. Check/Change build flags
  2. Configure
Note: MSVC supports build with multiple processes. Really. You can add -MP[processMax] flag. Details here.

For first step (are you really sure with "Static" tips?) we are going to %QTDIR%32-msvc2010 (I know that you know that real path is C:32-msvc2010 and if you have different version of MSVC it will be different spec directory ;)). Here we are interested in the qmake.conf configuration file.

Edit QMAKE_CFLAGS_RELEASE, QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO & QMAKE_CFLAGS_DEBUG variables. For example:

QMAKE_CFLAGS_RELEASE = -O2 -MD -MP2
QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO += -O2 -MD -Zi -MP2
QMAKE_CFLAGS_DEBUG = -Zi -MDd -MP2

Next — configuring. My configuration (shared) is:

 > configure -release -opensource -shared -ltcg -no-fast -exceptions -accessibility -stl -qt-sql-sqlite -no-qt3support 
-no-openvg -platform win32-msvc2010 -graphicssystem raster -qt-zlib -qt-gif -qt-libpng -qt-libmng -qt-libtiff 
-qt-libjpeg -no-dsp -no-vcproj -incredibuild-xge -plugin-manifests -qmake -process -rtti -mmx –3dnow -sse -sse2 
-openssl -no-dbus -phonon -phonon-backend -multimedia -audio-backend -webkit -script -scripttools -declarative 
-arch windows -qt-style-windows -qt-style-windowsxp -qt-style-windowsvista -no-style-plastique
-no-style-cleanlooks -no-style-motif -no-style-cde -no-style-windowsce -no-style-windowsmobile -no-style-s60 
-native-gestures

As you see, I do not want to build Qt3 support module, some styles, using image libs from Qt source, some additional instructions sets are enabled and some another stuff.

Configuring Qt Desktop

Ok, let’s configure… Accepting license… Please, wait… (building qmake now) :)

All the project’s files are read and now we able to build libs, tools, examples, etc. Just nmake it to build all. Also we are able to make only libs (nmake sub-src), tools (nmake sub-tools, but after libs)…

Recommendations

Copy (or move) OpenSSL libraries (*.dll) from %QTDIR% directory to Qt bin directory and add %QTDIR% to system %PATH% variable.

 > move OpenSSL\bin.dll Qt\bin

Reduce used HDD space

Attention! This operations removes debugging information! (if you set release-and-debug)

Just at %QTDIR% run nmake clean to delete all tmp objects, etc. Then rebuild translations (go to %QTDIR% and run nmake). And remove libraries (.dll) from %QTDIR%.

> cd Qt
> nmake clean
> cd translations
> nmake
> cd ..> del'''.dll