Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved

    Qt5OpenGL.lib(Qt5OpenGL.dll) : fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'X86'

    Installation and Deployment
    5
    8
    11504
    Loading More Posts
    • 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.
    • Z
      zyama last edited by

      Configuration: Win7(64), MSVS 2012, QT5.0.2(64)
      Trouble: a some problems with linking.

      <code>
      Generating Code...
      Compiling...
      moc_qwt_analog_clock.cpp
      moc_qwt_compass.cpp
      moc_qwt_counter.cpp
      moc_qwt_dial.cpp
      moc_qwt_knob.cpp
      moc_qwt_slider.cpp
      moc_qwt_thermo.cpp
      moc_qwt_wheel.cpp
      Generating Code...
      linking ..\lib\qwt.dll
      Qt5OpenGL.lib(Qt5OpenGL.dll) : fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'X86'
      NMAKE : fatal error U1077: 'echo' : return code '0x458'
      Stop.
      NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\BIN\nmake.exe"' : return code '0x2'
      Stop.
      NMAKE : fatal error U1077: 'cd' : return code '0x2'
      Stop.
      </code>

      1 Reply Last reply Reply Quote 0
      • SGaist
        SGaist Lifetime Qt Champion last edited by

        Hi and welcome to devnet,

        I would say that your are building your project in 32bit mode while linking to a 64bit Qt

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

        1 Reply Last reply Reply Quote 1
        • C
          Corvin last edited by

          How do I change the target for my project? Particularly, I am trying to build QWT and seeing this error.

          [quote author="SGaist" date="1367482099"]Hi and welcome to devnet,

          I would say that your are building your project in 32bit mode while linking to a 64bit Qt[/quote]

          1 Reply Last reply Reply Quote 0
          • SGaist
            SGaist Lifetime Qt Champion last edited by

            Hi and welcome to devnet,

            Select the win64 console in the Visual Studio submenus and configure/build Qwt from there, you should be good to go then

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

            1 Reply Last reply Reply Quote 0
            • C
              Corvin last edited by

              Qwt doesn't have a visual studio project attached, so I'm building from command line, using VS2010 compiler through qcc.

              Can you please suggest, how I should pull the qwt project into Visual Studio?

              [quote author="SGaist" date="1377982324"]Hi and welcome to devnet,

              Select the win64 console in the Visual Studio submenus and configure/build Qwt from there, you should be good to go then[/quote]

              1 Reply Last reply Reply Quote 0
              • SGaist
                SGaist Lifetime Qt Champion last edited by

                You can simply use the
                @
                qmake
                nmake
                @

                combo from the command line

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

                1 Reply Last reply Reply Quote 0
                • F
                  flip101 last edited by

                  You will also get this error on the console when you didn't select Qt with OpenGL during install (Qt 5.3.2). However when building with Qt creator it will additionally error: file not found.

                  1 Reply Last reply Reply Quote 0
                  • K
                    KeithS last edited by

                    If you are building from the command line, make sure you are using the 'VS2012 x64 Native Tools Command Prompt' (you'll find it under the Visual Studio menu in Start->All Programs).

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post