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. Qt 5.14 with VS2017 link error with QVector<QPointF>
Forum Updated to NodeBB v4.3 + New Features

Qt 5.14 with VS2017 link error with QVector<QPointF>

Scheduled Pinned Locked Moved Unsolved General and Desktop
4 Posts 2 Posters 425 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.
  • J Offline
    J Offline
    johnyang
    wrote on last edited by
    #1

    I came across this same issue as reported in https://bugreports.qt.io/browse/QTBUG-78112

    error LNK2019: unresolved external symbol "__declspec(dllimport) public: class QTypedArrayData<class QPointF>::iterator __thiscall QVector<class QPointF>::begin(class QTypedArrayData<class QPointF>::iterator)"
    

    It sounds like it is an issue with VS2017 itself. However, is there a workaround to bypass this problem? I don't quite understand when they are talking about disabling the option. Do I have to build Qt from source myself in order to bypass this problem?
    It's because I want to use the latest update on high dpi in Qt5.14. However, this makes my libraries failing to build with this link error.

    Anyone has come across this before and have a temporary solution?

    1 Reply Last reply
    0
    • VRoninV Offline
      VRoninV Offline
      VRonin
      wrote on last edited by
      #2

      Can you upgrade to VS2019? afaik MS adopded the "subscription" commercial offering since 2015 so the license you have allows you to always use the latest version

      "La mort n'est rien, mais vivre vaincu et sans gloire, c'est mourir tous les jours"
      ~Napoleon Bonaparte

      On a crusade to banish setIndexWidget() from the holy land of Qt

      J 1 Reply Last reply
      0
      • VRoninV VRonin

        Can you upgrade to VS2019? afaik MS adopded the "subscription" commercial offering since 2015 so the license you have allows you to always use the latest version

        J Offline
        J Offline
        johnyang
        wrote on last edited by johnyang
        #3

        @VRonin Unfortunately I can't move to VS2019 at the moment. Is there a workaround for VS2017?
        I have the source code of the 3rd party library I am having trouble to build.

        1 Reply Last reply
        0
        • J Offline
          J Offline
          johnyang
          wrote on last edited by
          #4

          I figured out that I just need to comment out -DQT_STRICT_ITERATORS and this error will go away.

          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