Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. C++98 warnings after update to Qt 5.14 (MSVS2019)
Forum Updated to NodeBB v4.3 + New Features

C++98 warnings after update to Qt 5.14 (MSVS2019)

Scheduled Pinned Locked Moved Unsolved Qt Creator and other tools
2 Posts 2 Posters 2.7k Views 2 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.
  • S Offline
    S Offline
    Szymon. M. Sabat
    wrote on last edited by
    #1

    After updating Qt to 5.15, I'm getting "incompatible with C++98" errors in ALL the places. I'm using CONFIG += c++1z (was using c++17 before but today I've learnt it apparently does nothing and the correct was is c++1z but the errors are there for both) and MSVS2019 (Qt MSVS2017 but it's compatible).

    Something changed? My app builds and runs the same, it's just that I'm getting all these warnings in every file, even Q_OBJECT macro is "unsupported" because of "nullptr" used there so you can imagine... I don't want to suppress all the warnings, I just want to get back to pre-upgrade state.

    aha_1980A 1 Reply Last reply
    0
    • S Szymon. M. Sabat

      After updating Qt to 5.15, I'm getting "incompatible with C++98" errors in ALL the places. I'm using CONFIG += c++1z (was using c++17 before but today I've learnt it apparently does nothing and the correct was is c++1z but the errors are there for both) and MSVS2019 (Qt MSVS2017 but it's compatible).

      Something changed? My app builds and runs the same, it's just that I'm getting all these warnings in every file, even Q_OBJECT macro is "unsupported" because of "nullptr" used there so you can imagine... I don't want to suppress all the warnings, I just want to get back to pre-upgrade state.

      aha_1980A Offline
      aha_1980A Offline
      aha_1980
      Lifetime Qt Champion
      wrote on last edited by aha_1980
      #2

      Hi @Szymon-M-Sabat,

      that was already mentioned in the blog post comments, there is also a workaround.

      You might want to look that up.

      Regards

      Qt has to stay free or it will die.

      1 Reply Last reply
      4

      • Login

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