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. Compile Errors Building Qt 4.6.3 With VS2008 For Windows x86_64 platforms

Compile Errors Building Qt 4.6.3 With VS2008 For Windows x86_64 platforms

Scheduled Pinned Locked Moved Installation and Deployment
5 Posts 4 Posters 5.4k 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.
  • E Offline
    E Offline
    elemings
    wrote on last edited by
    #1

    Greetings,

    I've run into a few compile errors while building Qt 4.6.3 for Windows x86_64 platforms with VS 2008. First, I should mention that I configured the build like this:

    @C:/Build/Qt/4.6.3-x86_64-vs2008> C:/Source/Qt/4.6.3/configure -prefix C:/Install/Qt/4.6.3 -debug_and_release -shared ...@

    The first errors I ran into were similar to this:

    @...
    qprocess.cpp
    c:/build/qt/4.6.3-x86_64-vs2008/include/qtcore/private/../../../../../../Source/Qt/4.6.3/src/corelib/io/qiodevice_p.h(161) : warning C4267: 'initializing' : conversion from 'size_t' to 'int', possible loss of data
    qtextstream.cpp
    c:/Install/Qt/4.6.3/src/corelib/io/qtextstream.cpp(3396) : fatal error C1083: Cannot open include file: 'qtextstream.moc': No such file or directory
    qtemporaryfile.cpp
    c:/build/qt/4.6.3-x86_64-vs2008/include/qtcore/private/../../../../../../Source/Qt/4.6.3/src/corelib/io/qiodevice_p.h(161) : warning C4267: 'initializing' : conversion from 'size_t' to 'int', possible loss of data
    qresource.cpp
    qresource_iterator.cpp
    ...@

    I determined that the moc_*.cpp source files were missing dependencies on the related *.moc files and were not therefore being generated. So I did a 'nmake mocables' and continued building until I hit my latest snag:

    @...
    moc_qanimationgroup.cpp
    moc_qsequentialanimationgroup.cpp
    tmp/moc/debug_shared/moc_qsequentialanimationgroup.cpp(85) : error C2027: use of undefined type 'QSequentialAnimationGroupPrivate'
    c:/build/qt/4.6.3-x86_64-vs2008/src/corelib/tmp/moc/debug_shared/../../../../../../../../Source/Qt/4.6.3/src/corelib/animation/qsequentialanimationgroup.h(56) : see declaration of 'QSequentialAnimationGroupPrivate'
    tmp/moc/debug_shared/moc_qsequentialanimationgroup.cpp(85) : error C2227: left of '->_q_uncontrolledAnimationFinished' must point to class/struct/union/generic type
    moc_qparallelanimationgroup.cpp
    tmp/moc/debug_shared/moc_qparallelanimationgroup.cpp(73) : error C2027: use of undefined type 'QParallelAnimationGroupPrivate'
    c:/build/qt/4.6.3-x86_64-vs2008/src/corelib/tmp/moc/debug_shared/../../../../../../../../Source/Qt/4.6.3/src/corelib/animation/qparallelanimationgroup.h(55) : see declaration of 'QParallelAnimationGroupPrivate'
    tmp/moc/debug_shared/moc_qparallelanimationgroup.cpp(73) : error C2227: left of '->_q_uncontrolledAnimationFinished' must point to class/struct/union/generic type
    moc_qpauseanimation.cpp
    ...@

    The problem is that the generated moc_*.cpp sources are not including the related private header files. I'm not sure what to do about this one. Anyone have any suggestions (other than "Don't build outside the source directory" or "Don't configure with an install prefix")?

    Thanks.

    1 Reply Last reply
    0
    • A Offline
      A Offline
      alexander
      wrote on last edited by
      #2

      “Don’t build outside the source directory” But why do you build outside?

      1 Reply Last reply
      0
      • E Offline
        E Offline
        elemings
        wrote on last edited by
        #3

        So multiple developers can build multiple configurations from the same source tree without wrecking your own or one another's builds.

        1 Reply Last reply
        0
        • R Offline
          R Offline
          rszabolcs
          wrote on last edited by
          #4

          I have almost the same problem. Did somebody find a solution? Thanks!

          1 Reply Last reply
          0
          • S Offline
            S Offline
            shixiaoyou
            wrote on last edited by
            #5

            Hello, have you fix this issue? can you tell me how to fix? i meet same issue.

            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