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. [SOLVED]Problem with Qt 5.5
QtWS25 Last Chance

[SOLVED]Problem with Qt 5.5

Scheduled Pinned Locked Moved General and Desktop
qt5.5migration
13 Posts 6 Posters 12.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.
  • M Offline
    M Offline
    mcosta
    wrote on 5 Jul 2015, 20:58 last edited by
    #3

    Hi,

    I think that you need to add some #include in your sources.
    DO you see some message related to your source files?

    Once your problem is solved don't forget to:

    • Mark the thread as SOLVED using the Topic Tool menu
    • Vote up the answer(s) that helped you to solve the issue

    You can embed images using (http://imgur.com/) or (http://postimage.org/)

    F 1 Reply Last reply 6 Jul 2015, 00:17
    0
    • H Offline
      H Offline
      Huulivoide
      wrote on 5 Jul 2015, 21:14 last edited by Huulivoide 7 May 2015, 21:17
      #4

      This might actually be a different problem, but in any case.

      There is some bug in Qt 5.5 and OSX. Fixed in 5.5.1.

      See the mailing list for more information.
      http://lists.qt-project.org/pipermail/interest/2015-July/017543.html

      1 Reply Last reply
      0
      • S Offline
        S Offline
        SGaist
        Lifetime Qt Champion
        wrote on 5 Jul 2015, 21:19 last edited by
        #5

        @Huulivoide it's not the same problem, the one from the mailing list is about a warning storm, here those are errors

        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
        0
        • F Offline
          F Offline
          freddy311082
          wrote on 6 Jul 2015, 00:03 last edited by
          #6

          Thank guys for you answers...

          I'm running OS X Yosemite with XCode 6.4...

          regards

          1 Reply Last reply
          0
          • M mcosta
            5 Jul 2015, 20:58

            Hi,

            I think that you need to add some #include in your sources.
            DO you see some message related to your source files?

            F Offline
            F Offline
            freddy311082
            wrote on 6 Jul 2015, 00:17 last edited by
            #7

            @mcosta said:

            Hi,

            I think that you need to add some #include in your sources.
            DO you see some message related to your source files?

            Hi my friend... why do you say that I'm missing some include ??

            regard

            M 1 Reply Last reply 6 Jul 2015, 05:20
            0
            • S Offline
              S Offline
              sandy.martel23
              wrote on 6 Jul 2015, 01:48 last edited by
              #8

              Those errors are all about C++11 constructs. You probably have some config in your .pro file trying to force an older C++ standard.
              Like removing C++11 or forcing stdlibc++ instead of libc++.

              1 Reply Last reply
              0
              • F freddy311082
                6 Jul 2015, 00:17

                @mcosta said:

                Hi,

                I think that you need to add some #include in your sources.
                DO you see some message related to your source files?

                Hi my friend... why do you say that I'm missing some include ??

                regard

                M Offline
                M Offline
                mcosta
                wrote on 6 Jul 2015, 05:20 last edited by
                #9

                @freddy311082

                Hi had a very similar problem when I moved my code from Qt 5.3 to 5.4; sometimes some #include are removed from Qt header files and the is needed to add in our code.

                Last question: "Are you compiling using C++11"??

                Once your problem is solved don't forget to:

                • Mark the thread as SOLVED using the Topic Tool menu
                • Vote up the answer(s) that helped you to solve the issue

                You can embed images using (http://imgur.com/) or (http://postimage.org/)

                1 Reply Last reply
                0
                • K Offline
                  K Offline
                  krekeltronics
                  wrote on 7 Jul 2015, 19:11 last edited by
                  #10

                  we are having the same issue on our build server (and yet different errors on the Windows side), and are indeed compiling with C++11. I have QMAKE_CXXFLAGS += -std=c++11 in the .pro file. Is that no longer correct/necessary?

                  M 1 Reply Last reply 7 Jul 2015, 19:44
                  0
                  • K krekeltronics
                    7 Jul 2015, 19:11

                    we are having the same issue on our build server (and yet different errors on the Windows side), and are indeed compiling with C++11. I have QMAKE_CXXFLAGS += -std=c++11 in the .pro file. Is that no longer correct/necessary?

                    M Offline
                    M Offline
                    mcosta
                    wrote on 7 Jul 2015, 19:44 last edited by
                    #11

                    @krekeltronics said:

                    QMAKE_CXXFLAGS += -std=c++1

                    Now you can use

                    CONFIG += c++11
                    

                    Once your problem is solved don't forget to:

                    • Mark the thread as SOLVED using the Topic Tool menu
                    • Vote up the answer(s) that helped you to solve the issue

                    You can embed images using (http://imgur.com/) or (http://postimage.org/)

                    1 Reply Last reply
                    0
                    • K Offline
                      K Offline
                      krekeltronics
                      wrote on 7 Jul 2015, 19:59 last edited by
                      #12

                      @mcosta said:

                      CONFIG += c++11

                      thanks. That resolved the C++11 errors (and should work for you as well @freddy311082 ). I've got a few other std-related things that didn't appear with the previous version, so I will post back if these seem to be core-related vs. necessary changes in our own code.

                      I do have the hundreds of clang diagnostic ignored "-Winconsistent-missing-override" now :)

                      1 Reply Last reply
                      0
                      • M Offline
                        M Offline
                        mcosta
                        wrote on 7 Jul 2015, 20:01 last edited by mcosta 7 Jul 2015, 20:01
                        #13

                        The warnings are related to a bug. Read here

                        Once your problem is solved don't forget to:

                        • Mark the thread as SOLVED using the Topic Tool menu
                        • Vote up the answer(s) that helped you to solve the issue

                        You can embed images using (http://imgur.com/) or (http://postimage.org/)

                        1 Reply Last reply
                        0

                        12/13

                        7 Jul 2015, 19:59

                        • Login

                        • Login or register to search.
                        12 out of 13
                        • First post
                          12/13
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • Users
                        • Groups
                        • Search
                        • Get Qt Extensions
                        • Unsolved