Important: Please read the Qt Code of Conduct -

Problems to install Qt 5.4.1 from offline installer and build a Qt project of vs2012 with the Qt vs add-in on Windows7-64bit

  • During struggling to set-up a Qt developing environment. I have encountered several issues to be considered.
    My Platform is as follows.

    • Windows7 64bit
    • Visual studio 2012 with Qt visual studio add-in 1.2.3
    1. A visual studio Qt project cannot be built when Qt is installed via an offline installer (I mean, exe)
    • It seems that Qt installation from "Qt 5.4.1 for Windows 64-bit (VS 2013, 722 MB) (info)" has some problems, so I failed to build the vs solution correctly. The following is the building error message of vs2012.

      1>------ 빌드 시작: 프로젝트: Test2, 구성: Debug x64 ------
      1> Moc'ing test2.h...
      1> Uic'ing test2.ui...
      1> Rcc'ing test2.qrc...
      1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(172,5): error MSB6006: "cmd.exe"이(가) 종 료되었습니다(코드: -1073741515).

    • According to, all pre-built binaries provided by the Qt downloading web page do not work in 64-bit environment, and it is the only way to download and build source code directly for setting up a Qt development environment. Is it correct?

    1. The latest version(1.2.4) of the Qt visual studio add-in contains some bugs, so vs2012 cannot load the Qt vs add-in.
    • I solved this problem by downgrading the version of Qt vs add-in from 1.2.4 to 1.2.3

    Setting up Qt developing environment makes me so tired...
    Now I am downloading the Qt source code and hoping direct building from source code works well.

  • I always build directly from source on Windows, Linux and Mac. I don't want all the bloatware that comes with Qt these days, just qtbase (inc. opengl) and qtsvg.

    Qt 5.3.1 compiles fine under VS2013 on Windows 7, both 32 and 64 bit. Even XP. I've had problems with 5.4.1 though, which are not yet resolved. Related to libGLES2v2.dll which should not be needed - I want desktop OpenGL, not ES2.

    Don't forget to use the VS 2013 Native Tools cmd prompt which sets up the VS variables you need...

Log in to reply