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. Unable to compile Qt 5.2.1 (Linker error)
Forum Updated to NodeBB v4.3 + New Features

Unable to compile Qt 5.2.1 (Linker error)

Scheduled Pinned Locked Moved General and Desktop
4 Posts 2 Posters 1.6k 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.
  • B Offline
    B Offline
    BenBenJones
    wrote on last edited by
    #1

    I'm trying to compile Qt 5.2.1 on a 64 Bit Win7 machine (I want 32 bit binaries).

    I configured

    @ configure -debug-and-release -opensource -platform win32-msvc2012 -opengl desktop -nomake examples -nomake tests
    @
    and I did set the compiler path by running

    @ C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\bin\vcvars32.bat@

    It compiles for a while but fails when linking.

    This is the error output:

    @ link /NOLOGO /DYNAMICBASE /NXCOMPAT /DEBUG /DLL /OUT:........\plugins\platforms\qwindowsd.dll @C:\Users\steffenh\AppData\Local\Temp\nm9509.tmp
    Creating library ........\plugins\platforms\qwindowsd.lib and object ........\plugins\platforms\qwindowsd.exp
    dlldata.obj : error LNK2001: unresolved external symbol _Accessible2_ProxyFileInfo
    dlldata.obj : error LNK2001: unresolved external symbol _AccessibleAction_ProxyFileInfo
    dlldata.obj : error LNK2001: unresolved external symbol _AccessibleApplication_ProxyFileInfo
    dlldata.obj : error LNK2001: unresolved external symbol _AccessibleComponent_ProxyFileInfo
    dlldata.obj : error LNK2001: unresolved external symbol _AccessibleEditableText_ProxyFileInfo
    dlldata.obj : error LNK2001: unresolved external symbol _AccessibleHyperlink_ProxyFileInfo
    dlldata.obj : error LNK2001: unresolved external symbol _AccessibleHypertext_ProxyFileInfo
    dlldata.obj : error LNK2001: unresolved external symbol _AccessibleImage_ProxyFileInfo
    dlldata.obj : error LNK2001: unresolved external symbol _AccessibleRelation_ProxyFileInfo
    dlldata.obj : error LNK2001: unresolved external symbol _AccessibleTable_ProxyFileInfo
    dlldata.obj : error LNK2001: unresolved external symbol _AccessibleTable2_ProxyFileInfo
    dlldata.obj : error LNK2001: unresolved external symbol _AccessibleTableCell_ProxyFileInfo
    dlldata.obj : error LNK2001: unresolved external symbol _AccessibleText_ProxyFileInfo
    dlldata.obj : error LNK2001: unresolved external symbol _AccessibleValue_ProxyFileInfo
    ........\plugins\platforms\qwindowsd.dll : fatal error LNK1120: 14 unresolved externals
    NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\BIN\link.EXE"' : return code '0x460'
    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.
    NMAKE : fatal error U1077: 'cd' : return code '0x2'
    Stop.
    NMAKE : fatal error U1077: 'cd' : return code '0x2'
    Stop.
    NMAKE : fatal error U1077: 'cd' : return code '0x2'
    Stop.
    NMAKE : fatal error U1077: 'cd' : return code '0x2'
    Stop.
    @

    It seems that Qt tries to link against Microsoft Active Accessibility, whose main file is "oleacc.dll", located in the system path, but it fails (the file is there, I checked)

    is there anyone who can help me?

    best,
    S.H

    1 Reply Last reply
    0
    • B Offline
      B Offline
      BenBenJones
      wrote on last edited by
      #2

      ... any ideas?

      1 Reply Last reply
      0
      • S Offline
        S Offline
        suslov.maxim
        wrote on last edited by
        #3

        I don't help, but I have a question: Why you can't download prebuilt Qt? What are reasons to compile Qt?

        1 Reply Last reply
        0
        • B Offline
          B Offline
          BenBenJones
          wrote on last edited by
          #4

          The linking worked when I added the VERBOSE linker flag via

          "QMAKE_LFLAGS += /VERBOSE" to "mkspecs/qconfig.pri"

          (This shouldn't change anything, but it worked).

          Qt Bug Description is here: https://bugreports.qt-project.org/si/jira.issueviews:issue-html/QTBUG-37910/QTBUG-37910.html

          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