Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. Trouble with MSVC2015

Trouble with MSVC2015

Scheduled Pinned Locked Moved Solved Qt Creator and other tools
4 Posts 2 Posters 3.7k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J.HilkJ Offline
    J.HilkJ Offline
    J.Hilk
    Moderators
    wrote on last edited by
    #1

    I've for a while now, used mingw to generate and debug my code and MSVC2015 release compiler to deploy on Windows.

    That seemed like a stupid thing to do, why not debug with MSVC too?
    So I went a head, followed the steps mentioned in this thread and added the debugger to my kit.

    So far so good. Sadly now my project does not compile neither in debug nor release mode.

    Everything has been restarted multiple times, clean build, there are no warnings or errors in my kits. screenshot

    If I remove the debugger, the release build does not compile either, so I guess WindowsSDK changed some files settings that I'm unaware of?

    Here's the compile output, hopefully someone can help me out here.

    sorry for the german-lines, I did change the language to english, but apparently not everything gets translated.

    //Release:
    
    	C:\Qt\5.8\msvc2015\bin\rcc.exe -name ressourcen ..\uConfig\ressourcen.qrc -o release\qrc_ressourcen.cpp
    	cl -BxC:\Qt\5.8\msvc2015\bin\qmake.exe -nologo -Zc:wchar_t -FS -Zc:strictStrings -Zc:throwingNew -O2 -MD -GR -W3 -w34100 -w34189 -w44996 -w44456 -w44457 -w44458 -wd4577 -wd4467 -E -Za ..\..\5.8\msvc2015\mkspecs\features\data\dummy.cpp 2>NUL >release\moc_predefs.h
    Code wird generiert...
    	rc -DUNICODE -DWIN32 -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_SERIALPORT_LIB -DQT_SERIALBUS_LIB -DQT_CONCURRENT_LIB -DQT_SQL_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DNDEBUG -fo release\uConfig_resource.res uConfig_resource.rc
    Der Befehl "rc" ist entweder falsch geschrieben oder
    konnte nicht gefunden werden.
    Code wird generiert...
    Code wird generiert...
    jom: C:\Qt\Projects\build-uConfig-Desktop_Qt_5_8_0_MSVC2015_32bit-Release\Makefile.Release [release\uConfig_resource.res] Error 1
    jom: C:\Qt\Projects\build-uConfig-Desktop_Qt_5_8_0_MSVC2015_32bit-Release\Makefile [release] Error 2
    07:39:57: The process "C:\Qt\Tools\QtCreator\bin\jom.exe" exited with code 2.
    Error while building/deploying project uConfig (kit: Desktop Qt 5.8.0 MSVC2015 32bit)
    When executing step "Make"
    07:39:57: Elapsed time: 00:55.
    
    //Debug
    
    	C:\Qt\5.8\msvc2015\bin\rcc.exe -name ressourcen ..\uConfig\ressourcen.qrc -o debug\qrc_ressourcen.cpp
    	cl -BxC:\Qt\5.8\msvc2015\bin\qmake.exe -nologo -Zc:wchar_t -FS -Zc:strictStrings -Zc:throwingNew -Zi -MDd -GR -W3 -w34100 -w34189 -w44996 -w44456 -w44457 -w44458 -wd4577 -wd4467 -E -Za ..\..\5.8\msvc2015\mkspecs\features\data\dummy.cpp 2>NUL >debug\moc_predefs.h
    	rc -D_DEBUG -DUNICODE -DWIN32 -DQT_DEPRECATED_WARNINGS -DQT_QML_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_SERIALPORT_LIB -DQT_SERIALBUS_LIB -DQT_CONCURRENT_LIB -DQT_SQL_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -fo debug\uConfig_resource.res uConfig_resource.rc
    Der Befehl "rc" ist entweder falsch geschrieben oder
    konnte nicht gefunden werden.
    diowidget.cpp
    cstackedwidget.cpp
    Code wird generiert...
    Code wird generiert...
    Code wird generiert...
    jom: C:\Qt\Projects\build-uConfig-Desktop_Qt_5_8_0_MSVC2015_32bit-Debug\Makefile.Debug [debug\uConfig_resource.res] Error 1
    jom: C:\Qt\Projects\build-uConfig-Desktop_Qt_5_8_0_MSVC2015_32bit-Debug\Makefile [debug] Error 2
    07:42:34: The process "C:\Qt\Tools\QtCreator\bin\jom.exe" exited with code 2.
    Error while building/deploying project uConfig (kit: Desktop Qt 5.8.0 MSVC2015 32bit)
    When executing step "Make"
    07:42:34: Elapsed time: 00:16.
    

    Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


    Q: What's that?
    A: It's blue light.
    Q: What does it do?
    A: It turns blue.

    1 Reply Last reply
    0
    • J.HilkJ Offline
      J.HilkJ Offline
      J.Hilk
      Moderators
      wrote on last edited by J.Hilk
      #2

      Problem solved:

      maintenance tool -> uninstall MSVC-components -> Reboot -> MaintenanceTool -> install MSVC-components. + Manual delete off all non *.h/cpp files.

      Celebrated too early....


      Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


      Q: What's that?
      A: It's blue light.
      Q: What does it do?
      A: It turns blue.

      1 Reply Last reply
      0
      • J.HilkJ Offline
        J.HilkJ Offline
        J.Hilk
        Moderators
        wrote on last edited by J.Hilk
        #3

        Sometimes you have to do things yourself to make sure its done right.

        First of this StackOverflow entry was very helpfull.

        So I added ...\Windows Kits\10\bin\x86 to my path variable.
        Windows Kit itself only linked Windows Performance Toolkit there.

        and copied rc.exe and rcdll.dll from the WindowsSDK folder to VC\bin problem solved...

        If a mod could change this back to Solved, I would appreciate it. I kind of messed that one up earlier today.


        Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


        Q: What's that?
        A: It's blue light.
        Q: What does it do?
        A: It turns blue.

        K 1 Reply Last reply
        0
        • J.HilkJ J.Hilk

          Sometimes you have to do things yourself to make sure its done right.

          First of this StackOverflow entry was very helpfull.

          So I added ...\Windows Kits\10\bin\x86 to my path variable.
          Windows Kit itself only linked Windows Performance Toolkit there.

          and copied rc.exe and rcdll.dll from the WindowsSDK folder to VC\bin problem solved...

          If a mod could change this back to Solved, I would appreciate it. I kind of messed that one up earlier today.

          K Offline
          K Offline
          koahnig
          wrote on last edited by
          #4

          @J.Hilk

          Change to solved on your request.
          The thread was marked as discussion and had to be changed to "ask question" for setting to "solved".

          Vote the answer(s) that helped you to solve your issue(s)

          1 Reply Last reply
          1

          • Login

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Users
          • Groups
          • Search
          • Get Qt Extensions
          • Unsolved