Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. Where to specify Zielcomputertyp "X64" - LNK1112 Error
Forum Updated to NodeBB v4.3 + New Features

Where to specify Zielcomputertyp "X64" - LNK1112 Error

Scheduled Pinned Locked Moved Unsolved Installation and Deployment
9 Posts 5 Posters 5.0k Views 2 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.
  • D Offline
    D Offline
    DirkM
    wrote on last edited by
    #1

    Hi,

    I'm in progress of reinstalling and updating my QT environment as it didn't want to work anymore with formerly installed MSVC2015 x64 and current Win 10 Pro build.

    My environment contains:
    Windows 10 Pro Build 14393
    Qt Creator 4.4.1 based on 5.9.2
    I worked through some compiler issues yesterday and came to the point, that I'm getting this error message:

    Qt5Widgetsd.lib(Qt5Widgetsd.dll) : fatal error LNK1112: Modul-Computertyp "x64" steht in Konflikt mit dem Zielcomputertyp "X86".
    

    My target is to be able to compile and run my application in 64-bit architecture.
    It looks to me like there is still one small setting to be adjusted, but I can't find the setting in Qt to do so.
    The full linking output is:

    10:02:58: Führe Schritte für Projekt untitled aus...
    10:02:58: Unveränderte Konfiguration, qmake-Schritt wird übersprungen.
    10:02:58: Starte "Y:\Mirrow\Qt\Tools\QtCreator\bin\jom.exe" 
    	Y:\Mirrow\Qt\Tools\QtCreator\bin\jom.exe -f Makefile.Debug
    	link /NOLOGO /DYNAMICBASE /NXCOMPAT /DEBUG /SUBSYSTEM:WINDOWS "/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='*' processorArchitecture='*'" /MANIFEST:embed /OUT:debug\untitled.exe @C:\Users\Dirk\AppData\Local\Temp\untitled.exe.4636.16.jom
    Qt5Widgetsd.lib(Qt5Widgetsd.dll) : fatal error LNK1112: Modul-Computertyp "x64" steht in Konflikt mit dem Zielcomputertyp "X86".
    jom: C:\temp\build-untitled-Desktop_Qt_5_9_2_MSVC2015_64bit-Debug\Makefile.Debug [debug\untitled.exe] Error 1112
    jom: C:\temp\build-untitled-Desktop_Qt_5_9_2_MSVC2015_64bit-Debug\Makefile [debug] Error 2
    10:03:02: Der Prozess "Y:\Mirrow\Qt\Tools\QtCreator\bin\jom.exe" wurde mit dem Rückgabewert 2 beendet.
    Fehler beim Erstellen/Deployment des Projekts untitled (Kit: Desktop Qt 5.9.2 MSVC2015 64bit)
    Bei der Ausführung von Schritt "Make"
    10:03:02: Verstrichene Zeit: 00:04.
    

    Qt automatically created the MSVC 2015 Kit but did not assign the compiler properly. So I've finished the kit by choosing the following configuration:

    0_1508058301843_518441b5-850c-497c-9836-3888ceea13b2-grafik.png ![alt text](image url)

    My pro-file looks like this now:

    #-------------------------------------------------
    #
    # Project created by QtCreator 2017-10-14T13:52:00
    #
    #-------------------------------------------------
    
    QT       += core gui
    
    greaterThan(QT_MAJOR_VERSION, 4): QT += widgets
    
    TARGET = untitled
    TEMPLATE = app
    
    # The following define makes your compiler emit warnings if you use
    # any feature of Qt which has been marked as deprecated (the exact warnings
    # depend on your compiler). Please consult the documentation of the
    # deprecated API in order to know how to port your code away from it.
    DEFINES += QT_DEPRECATED_WARNINGS
    
    # You can also make your code fail to compile if you use deprecated APIs.
    # In order to do so, uncomment the following line.
    # You can also select to disable deprecated APIs only up to a certain version of Qt.
    #DEFINES += QT_DISABLE_DEPRECATED_BEFORE=0x060000    # disables all the APIs deprecated before Qt 6.0.0
    
    
    SOURCES += \
            main.cpp \
            mainwindow.cpp
    
    HEADERS += \
            mainwindow.h
    
    FORMS += \
            mainwindow.ui
    
    CONFIG += mobility
    MOBILITY = 
    
    
    win32: LIBS += -L$$PWD/'../../Program Files (x86)/Windows Kits/10/Lib/10.0.15063.0/um/x64/' -lshell32
    
    INCLUDEPATH += $$PWD/'../../Program Files (x86)/Windows Kits/10/Lib/10.0.15063.0/um/x64'
    DEPENDPATH += $$PWD/'../../Program Files (x86)/Windows Kits/10/Lib/10.0.15063.0/um/x64'
    
    win32:!win32-g++: PRE_TARGETDEPS += $$PWD/'../../Program Files (x86)/Windows Kits/10/Lib/10.0.15063.0/um/x64/shell32.lib'
    else:win32-g++: PRE_TARGETDEPS += $$PWD/'../../Program Files (x86)/Windows Kits/10/Lib/10.0.15063.0/um/x64/libshell32.a'
    

    I couldn't find the solution how to properly change the target environment to x64 while the Kit has already set everything I can see to x64. Help is highly appreciated. Thanks.

    Dirk

    jsulmJ 1 Reply Last reply
    0
    • D DirkM

      Hi,

      I'm in progress of reinstalling and updating my QT environment as it didn't want to work anymore with formerly installed MSVC2015 x64 and current Win 10 Pro build.

      My environment contains:
      Windows 10 Pro Build 14393
      Qt Creator 4.4.1 based on 5.9.2
      I worked through some compiler issues yesterday and came to the point, that I'm getting this error message:

      Qt5Widgetsd.lib(Qt5Widgetsd.dll) : fatal error LNK1112: Modul-Computertyp "x64" steht in Konflikt mit dem Zielcomputertyp "X86".
      

      My target is to be able to compile and run my application in 64-bit architecture.
      It looks to me like there is still one small setting to be adjusted, but I can't find the setting in Qt to do so.
      The full linking output is:

      10:02:58: Führe Schritte für Projekt untitled aus...
      10:02:58: Unveränderte Konfiguration, qmake-Schritt wird übersprungen.
      10:02:58: Starte "Y:\Mirrow\Qt\Tools\QtCreator\bin\jom.exe" 
      	Y:\Mirrow\Qt\Tools\QtCreator\bin\jom.exe -f Makefile.Debug
      	link /NOLOGO /DYNAMICBASE /NXCOMPAT /DEBUG /SUBSYSTEM:WINDOWS "/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='*' processorArchitecture='*'" /MANIFEST:embed /OUT:debug\untitled.exe @C:\Users\Dirk\AppData\Local\Temp\untitled.exe.4636.16.jom
      Qt5Widgetsd.lib(Qt5Widgetsd.dll) : fatal error LNK1112: Modul-Computertyp "x64" steht in Konflikt mit dem Zielcomputertyp "X86".
      jom: C:\temp\build-untitled-Desktop_Qt_5_9_2_MSVC2015_64bit-Debug\Makefile.Debug [debug\untitled.exe] Error 1112
      jom: C:\temp\build-untitled-Desktop_Qt_5_9_2_MSVC2015_64bit-Debug\Makefile [debug] Error 2
      10:03:02: Der Prozess "Y:\Mirrow\Qt\Tools\QtCreator\bin\jom.exe" wurde mit dem Rückgabewert 2 beendet.
      Fehler beim Erstellen/Deployment des Projekts untitled (Kit: Desktop Qt 5.9.2 MSVC2015 64bit)
      Bei der Ausführung von Schritt "Make"
      10:03:02: Verstrichene Zeit: 00:04.
      

      Qt automatically created the MSVC 2015 Kit but did not assign the compiler properly. So I've finished the kit by choosing the following configuration:

      0_1508058301843_518441b5-850c-497c-9836-3888ceea13b2-grafik.png ![alt text](image url)

      My pro-file looks like this now:

      #-------------------------------------------------
      #
      # Project created by QtCreator 2017-10-14T13:52:00
      #
      #-------------------------------------------------
      
      QT       += core gui
      
      greaterThan(QT_MAJOR_VERSION, 4): QT += widgets
      
      TARGET = untitled
      TEMPLATE = app
      
      # The following define makes your compiler emit warnings if you use
      # any feature of Qt which has been marked as deprecated (the exact warnings
      # depend on your compiler). Please consult the documentation of the
      # deprecated API in order to know how to port your code away from it.
      DEFINES += QT_DEPRECATED_WARNINGS
      
      # You can also make your code fail to compile if you use deprecated APIs.
      # In order to do so, uncomment the following line.
      # You can also select to disable deprecated APIs only up to a certain version of Qt.
      #DEFINES += QT_DISABLE_DEPRECATED_BEFORE=0x060000    # disables all the APIs deprecated before Qt 6.0.0
      
      
      SOURCES += \
              main.cpp \
              mainwindow.cpp
      
      HEADERS += \
              mainwindow.h
      
      FORMS += \
              mainwindow.ui
      
      CONFIG += mobility
      MOBILITY = 
      
      
      win32: LIBS += -L$$PWD/'../../Program Files (x86)/Windows Kits/10/Lib/10.0.15063.0/um/x64/' -lshell32
      
      INCLUDEPATH += $$PWD/'../../Program Files (x86)/Windows Kits/10/Lib/10.0.15063.0/um/x64'
      DEPENDPATH += $$PWD/'../../Program Files (x86)/Windows Kits/10/Lib/10.0.15063.0/um/x64'
      
      win32:!win32-g++: PRE_TARGETDEPS += $$PWD/'../../Program Files (x86)/Windows Kits/10/Lib/10.0.15063.0/um/x64/shell32.lib'
      else:win32-g++: PRE_TARGETDEPS += $$PWD/'../../Program Files (x86)/Windows Kits/10/Lib/10.0.15063.0/um/x64/libshell32.a'
      

      I couldn't find the solution how to properly change the target environment to x64 while the Kit has already set everything I can see to x64. Help is highly appreciated. Thanks.

      Dirk

      jsulmJ Offline
      jsulmJ Offline
      jsulm
      Lifetime Qt Champion
      wrote on last edited by
      #2

      @DirkM Did you try to delete the build directory, run qmake and rebuild?

      https://forum.qt.io/topic/113070/qt-code-of-conduct

      D 1 Reply Last reply
      0
      • D Offline
        D Offline
        DirkM
        wrote on last edited by
        #3
        This post is deleted!
        1 Reply Last reply
        0
        • jsulmJ jsulm

          @DirkM Did you try to delete the build directory, run qmake and rebuild?

          D Offline
          D Offline
          DirkM
          wrote on last edited by
          #4

          @jsulm
          Just to be sure I cleared the folder, executed qmake and compiled again. Same issue. :-(

          1 Reply Last reply
          0
          • SGaistS Offline
            SGaistS Offline
            SGaist
            Lifetime Qt Champion
            wrote on last edited by
            #5

            Hi,

            Do you also get that with a default project ?

            Interested in AI ? www.idiap.ch
            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

            D 1 Reply Last reply
            0
            • SGaistS SGaist

              Hi,

              Do you also get that with a default project ?

              D Offline
              D Offline
              DirkM
              wrote on last edited by
              #6

              @SGaist Yes, I do. Actually I'm just setting up the environment with a default project 'untitled1'.

              J.HilkJ 1 Reply Last reply
              0
              • D DirkM

                @SGaist Yes, I do. Actually I'm just setting up the environment with a default project 'untitled1'.

                J.HilkJ Offline
                J.HilkJ Offline
                J.Hilk
                Moderators
                wrote on last edited by
                #7

                @DirkM
                hi,

                when you configure your Project, make sure, that in "Buid-Umgebung" your path variable contains the
                the windows 10 kit

                eg:
                C:\Program Files (x86)\Windows Kits\10\bin\x86;

                0_1508222354559_path.PNG

                that is not automatically added when you install the msvc debugger

                I ran into the same problem.


                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.

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

                  @DirkM
                  hi,

                  when you configure your Project, make sure, that in "Buid-Umgebung" your path variable contains the
                  the windows 10 kit

                  eg:
                  C:\Program Files (x86)\Windows Kits\10\bin\x86;

                  0_1508222354559_path.PNG

                  that is not automatically added when you install the msvc debugger

                  I ran into the same problem.

                  D Offline
                  D Offline
                  DirkM
                  wrote on last edited by
                  #8

                  @J.Hilk Thanks for the hint. I added the path (after checking that it exists on my maschine.), cleared the directory, execute qmake and compile. Unfortunately it didn't work. I also tried the path with exchanging x86 to x64. Do you have any other idea?

                  My environment configuration looks like this:

                  0_1508268875216_9d35330c-731d-42de-a5af-d1678020e71b-grafik.png
                  0_1508268910399_c3661a08-1ba1-44db-ae2b-1cf46b4aeac0-grafik.png
                  0_1508268950478_6451224a-e2e6-4e34-8b52-7820842a930e-grafik.png

                  1 Reply Last reply
                  0
                  • G4banditG Offline
                    G4banditG Offline
                    G4bandit
                    wrote on last edited by G4bandit
                    #9

                    Hmm no timestamp? howeever 17.11.23

                    I had a similar issue with this Link Error:

                    Qt5Widgetsd.lib(Qt5Widgetsd.dll):-1: Fehler: LNK1112: Modul-Computertyp "x86" steht in Konflikt mit dem Zielcomputertyp "x64".

                    This message Pop up when I try to compile with the following setting
                    0_1511425158114_SettingMSVC2015_32bit.png

                    Even when I adjust it "more correct" to ...MSVC2015 32bit like this
                    0_1511425313879_SettingMSVC2015_32bit_MoreCorrectSetting.png

                    The message stay the same. I think it has to do with this line from (Projekte->Build-Umgebung)
                    C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\bin\HostX64\x64;

                    So for me the solution was to use this Setting

                    0_1511425440418_SettingMSVC2015_64bit.png

                    I have a 64bit machine so it make sense. So my resume is do not set up 64Bit stuff inside of 32Bit?QtPlugins? And I am not able to use a 32Bit Debugger on my 64Bit machine.
                    OR expand the Microsoft Visual Studio\2017\Community\VC\Tools to HostX86\x86.

                    1 Reply Last reply
                    0

                    • Login

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