Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Intel C++ problem with Qt 5.7.1
QtWS25 Last Chance

Intel C++ problem with Qt 5.7.1

Scheduled Pinned Locked Moved Solved General and Desktop
2 Posts 1 Posters 462 Views
  • 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
    DeadParrot
    wrote on last edited by DeadParrot
    #1

    Hello,

    After I updated from Qt 5.7.0 to 5.7.1 my Intel C++ 2016 application builds were failing due to qMove not being defined to std::move, at least at the point of qimage.h inclusion. I don't see a change in qcompilerdetection.h that is relevant so I'm not sure what is going on. I worked around the problem by replacing qMove with std::move in qimage.h.

    My build environment and .pro files have not changed and, as before, I compile with /Qstd=c++11 so I'm perplexed.

    This is on Windows 10 doing 64-bit builds and using the msvc2015_64 support in Qt 5.7.1.

    Any ideas? Thanks!

    D 1 Reply Last reply
    0
    • D DeadParrot

      Hello,

      After I updated from Qt 5.7.0 to 5.7.1 my Intel C++ 2016 application builds were failing due to qMove not being defined to std::move, at least at the point of qimage.h inclusion. I don't see a change in qcompilerdetection.h that is relevant so I'm not sure what is going on. I worked around the problem by replacing qMove with std::move in qimage.h.

      My build environment and .pro files have not changed and, as before, I compile with /Qstd=c++11 so I'm perplexed.

      This is on Windows 10 doing 64-bit builds and using the msvc2015_64 support in Qt 5.7.1.

      Any ideas? Thanks!

      D Offline
      D Offline
      DeadParrot
      wrote on last edited by
      #2

      This was reported as a Qt bug: https://bugreports.qt.io/browse/QTBUG-57915.

      A link to a related bug and a patch that solves this issue can be found at that bug report.

      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