Creating Qt on Windows 7 with Visual Studio 2010

Could anyone build Qt on Windows 7 (64-bit) with Visual Studio 2010? I tried different compilers and a parameter -no-webkitfor configure, but every time nmake fails with error code U1077. It would be very helpful for suggestions.

+5
source share
2 answers

I successfully compiled the 64-bit version of Qt 4.7.2 (minimum) on the 64-bit version of Windows 7 (Ultimate) with VS2010 SP1 + Windows SDK 7.1 (64-bit release environment).


> The installation procedure was recommended:

1. Visual Studio 2010
2. Windows SDK 7.1
3. Visual Studio 2010 SP1
4. Update compiler Visual C ++ 2010 SP1 for Windows SDK 7.1


VS2010 were switched to use Windows SDK 7.1 as a set of platform tools for default:

"C:\Program Files\Microsoft SDKs\Windows\v7.1\Setup\WindowsSdkVer.exe" -version:v7.1


64-bit version of OpenSSL was compiled as described here:

http://wiki.qt.io/Building_Qt_Desktop_for_Windows_with_MSVC#Building_OpenSSL

and here:

http://wiki.openssl.org/index.php/Compilation_and_Installation#W64


Installation path for the 64-bit version of OpenSSL:

"C: \ Program Files \ OpenSSL" The


contents of qt-everywhere-opensource-src-4.7.2.zip were unpacked here:

"C: \ Program Files \ Nokia \ Qt 4.7.2"


To To set up the build environment, I used the batch script package (setqtbuildenv.cmd) with the following contents: And finally, the nmake command was used.

@echo off
echo Setting Microsoft Windows SDK 7.1 Environment set WINSDKDIR=C:\Program Files\Microsoft SDKs\Windows\v7.1 call "%WINSDKDIR%\Bin\SetEnv.cmd" /Release /x64 /win7
echo Setting OpenSSL Environment set OPENSSLDIR=C:\PROGRA~1\OpenSSL set PATH=%OPENSSLDIR%\bin;%PATH% set LIB=%OPENSSLDIR%\lib;%LIB% set INCLUDE=%OPENSSLDIR%\include;%INCLUDE%
echo Setting Qt Environment set QTDIR=C:\PROGRA~1\Nokia\QT47~1.2 set PATH=%PATH%;%QTDIR%\bin
cd /d "%QTDIR%"
configure.exe -release -opensource -shared -platform win32-msvc2010 -no-webkit -no-phonon -no-phonon-backend -no-script -no-scripttools -no-qt3support -no-multimedia -no-ltcg



+3
source

I had the same problem, eventually abandoned the source code and used the binary instead. It works just fine so far (since I only use it for my graphic course project)

+1
source

All Articles