Help installing QT for VSE2012

ArbolOne · wrote on 5 Feb 2014, 01:10

I am having problem compiling using qt-creator. I have seen this abnormalities, please look at this images

https://skydrive.live.com/?cid=1ecc73232b89516a#cid=1ECC73232B89516A&id=1ECC73232B89516A!107

Thanks

ArbolOne · wrote on 5 Feb 2014, 01:47

I see now, the problem is that Qt could not find the debugger for VSE2012 (CDB ), so what is the name of the debugger and where would I find it?

TIA

podsvirov · wrote on 5 Feb 2014, 04:44

Try install "Windows Software Development Kit":http://msdn.microsoft.com/en-us/windows/hardware/hh852363.aspx
Then seek debugger in path like: "C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\cdb.exe"

ArbolOne · wrote on 5 Feb 2014, 18:28

Thanks for replying.
There is a variety of SDKs and I am bit uncertain as to which SDK to use/download. I am using Win7-64 and I intend to use VSExpress2012 with qt-windows-opensource-5.2.0-msvc2012-x86_64-offline as my development tools. As a side note, I wish Qt would have been able to use VSExpress2013, but it is what it is.
Again, thanks for the help!

ArbolOne · wrote on 6 Feb 2014, 00:57

I did what Konstantin suggested, but now I get this message:
@19:47:14: Running steps for project Qt_Widget_Test...
19:47:14: Configuration unchanged, skipping qmake step.
19:47:14: Starting: "C:\Qt\Qt5.2.0\Tools\QtCreator\bin\jom.exe"
C:\Qt\Qt5.2.0\Tools\QtCreator\bin\jom.exe -f Makefile.Debug
cl -c -nologo -Zm200 -Zc:wchar_t -Zi -MDd -GR -W3 -w34100 -w34189 -EHsc -DUNICODE -DWIN32 -DQT_QML_DEBUG -DQT_DECLARATIVE_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_OPENGL_ES_2 -DQT_OPENGL_ES_2_ANGLE -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\include" -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\include\QtWidgets" -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\include\QtGui" -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\include\QtANGLE" -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\include\QtCore" -I"debug" -I"." -I"." -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\mkspecs\win32-msvc2012" -Fodebug\ @C:\Users\ARBOLO~1\AppData\Local\Temp\main.obj.20708.15.jom
'cl' is not recognized as an internal or external command,
operable program or batch file.
jom: C:\Dev\c++\build-Qt_Widget_Test-Desktop_Qt_5_2_0_MSVC2012_64bit-Debug\Makefile.Debug [debug\main.obj] Error 1
cl -c -nologo -Zm200 -Zc:wchar_t -Zi -MDd -GR -W3 -w34100 -w34189 -EHsc -DUNICODE -DWIN32 -DQT_QML_DEBUG -DQT_DECLARATIVE_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_OPENGL_ES_2 -DQT_OPENGL_ES_2_ANGLE -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\include" -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\include\QtWidgets" -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\include\QtGui" -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\include\QtANGLE" -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\include\QtCore" -I"debug" -I"." -I"." -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\mkspecs\win32-msvc2012" -Fodebug\ @C:\Users\ARBOLO~1\AppData\Local\Temp\mainwindow.obj.20708.62.jom
'cl' is not recognized as an internal or external command,
operable program or batch file.
jom: C:\Dev\c++\build-Qt_Widget_Test-Desktop_Qt_5_2_0_MSVC2012_64bit-Debug\Makefile.Debug [debug\mainwindow.obj] Error 1
jom: C:\Dev\c++\build-Qt_Widget_Test-Desktop_Qt_5_2_0_MSVC2012_64bit-Debug\Makefile [debug] Error 2
19:47:15: The process "C:\Qt\Qt5.2.0\Tools\QtCreator\bin\jom.exe" exited with code 2.
Error while building/deploying project Qt_Widget_Test (kit: Desktop Qt 5.2.0 MSVC2012 64bit)
When executing step 'Make'
19:47:15: Elapsed time: 00:00.@

podsvirov · wrote on 6 Feb 2014, 05:25

Try to remove a tick: Tools->Options->Build & Run->General "Use jom instead of nmake".

ArbolOne · wrote on 6 Feb 2014, 13:45

I tried that, but to no avail.
I have noticed that Tools->Options->Build & Run->Debugger shows that an old installation, but no longer existing GDB as the first debugger, second and third are the CDB in the ..\Windows Kits\8.1\Debuggers. I would like to remove the line for the GDB and leave the one for CDB x64 as the first choice. Can you help me with that?

podsvirov · wrote on 6 Feb 2014, 15:58

You have installed VSE2012?
In Qt Creator you must configure: Tools->Options->Build & Run
a) Compiler
b) Debugger
c) Qt
d) Kit (Compiler, Debuger and Qt)
Then use Kit in you project.

ArbolOne · wrote on 8 Feb 2014, 02:58

Thanks again Konstantin.
Points a, b & d are completed by Qt's autodetection. I don't know what you mean in point 'c'.
The problem here is that Qt is reading a file that is part of the previous Qt installation. I had installed Qt-MinGW, but I removed that installation in favour of Qt-VSEx-2012. Among the files installed with Qt-MinGW is one that was not deleted when I uninstalled Qt-MinGW, now Qt- VSE2012 is reading it as part of its installation, obviously QT-VSE2012 is wrong and should not read that file.
The solution would be to find the file and delete it myself or make sure that Qt-VSE2012 does not read that file. It would be nice if I could delete the entry in Tools->Options->Build & Run but Qt does not allow me.

Now, in regards to the errors, I don't know what is causing those errors.

Error 1
C:\Qt\Qt5.2.0\Tools\QtCreator\bin\jom.exe -f Makefile.Debug
cl -c -nologo -Zm200 -Zc:wchar_t -Zi -MDd -GR -W3 -w34100 -w34189 -EHsc -DUNICODE -DWIN32 -DQT_QML_DEBUG -DQT_DECLARATIVE_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_OPENGL_ES_2 -DQT_OPENGL_ES_2_ANGLE -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\include" -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\include\QtWidgets" -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\include\QtGui" -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\include\QtANGLE" -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\include\QtCore" -I"debug" -I"." -I"." -I"......\Qt\Qt5.2.0\5.2.0\msvc2012_64\mkspecs\win32-msvc2012" -Fodebug\ @C:\Users\ARBOLO~1\AppData\Local\Temp\main.obj.39072.16.jom
'cl' is not recognized as an internal or external command,
operable program or batch file.
jom: C:\Dev\c++\build-Qt_Widget_Test-Desktop_Qt_5_2_0_MSVC2012_64bit-Debug\Makefile.Debug [debug\main.obj] Error 1

If I switch to nmake, I get this error:
21:56:50: Running steps for project Qt_Widget_Test...
21:56:50: Starting: "nmake.exe" clean
qtcreator_ctrlc_stub: Command line failed: nmake.exe clean
21:56:50: The process "nmake.exe" exited with code -1.
21:56:50: Configuration unchanged, skipping qmake step.
21:56:50: Starting: "nmake.exe"
qtcreator_ctrlc_stub: Command line failed: nmake.exe
21:56:50: The process "nmake.exe" exited with code -1.
Error while building/deploying project Qt_Widget_Test (kit: Desktop Qt 5.2.0 MSVC2012 64bit)
When executing step 'Make'
21:56:50: Elapsed time: 00:00.

podsvirov · wrote on 9 Feb 2014, 11:40

Environment allows to build a project with different compilers.
It's okay if you "Build & Run" a lot of different records.
For cleaning specific project settings, you can manually delete the files *.pro.user *

By your description it seems to me that you have a problem with the compiler.

Compiler and debugger MSVC installed separately.

ArbolOne · wrote on 9 Feb 2014, 18:00

Thank you Konstantin for you help
The problem is neither the debugger nor the compiler, and even less of a problem is the operating system. The problem is Qt.
But who am I to make such statement? specially when I have never used Qt. This alone disqualify me to make any positive or negative statements about Qt. However, my observation is not about Qt's functionality, my observation is about Qt's inability to even exist in a Windows OS, my observation is about the Qt's false statement regarding its functionality with Visual Studio/VC++ and, I am afraid that this dysfunctionality might even exists in under Win-OS.
Java promises to have been created to work under any OS in which its VM is installed. Qt makes a similar promise saying that its code would work on Win, *nix, etc. When it comes to Java all we do is install the Java tool-kit, write the program and watch it run. However, when it comes to Qt, one has to install Qt tool kit, and then... nothing, all we have to do is watch how Qt does not work, at least for us who are locked on VS2012 or just VC++. I know that no developer would be interested in making millions developing for Linux, but we give it a good shut at it if we develop for Win-OS, and if the developed application can also work on a mobile hardware, we have a much better chance. Well, Qt promises to make this dream come true, but nothing could be further from the truth. I don't know if Mac's developers have the same problem, as I have as a Win-OS developer, but I have never met a Mac developer telling me how wonderful Qt is, all I know is *nix developers telling me how beautiful Trolltek-Qt was. Qt is using the hype about Mobile Apps, portability and money making possibility to attract developers, but no, no man, non of these is true.
I am sure that there will be many posters saying me otherwise, but while they might be regurgitation what Qt sells, I am only stating what my experience has shown me.
Again, thank you so very much for all the help you have provided me with. I will keep in mind your professionalism and good character.