Details
-
Task
-
Resolution: Unresolved
-
P3: Somewhat important
-
6.4.0 Beta1
-
None
-
-
13
-
2c0120d35 (dev), a3ff421d2 (dev), 4786eb0b0 (dev), c58680d7a (dev), a877059c9 (dev)
-
Foundation PM Prioritized
Description
While trying to enable builds with QT_DISABLE_DEPRECATED_UP_TO, I noticed that we have a lot of places where the proper deprecation warning is missing, so we still keep using the old API. In some other places the warning is explicitly silenced. All such places will result in hard compiler errors when building with QT_DISABLE_DEPRECATED_UP_TO >= the deprecation version.
Once we have the possibility to set QT_DISABLE_DEPRECATED_UP_TO as a configure parameter, we need to enable at least one build (ideally - one for each platform) with QT_DISABLE_DEPRECATED_UP_TO = Current Qt version, to make sure that we do the deprecation correctly. Otherwise this feature will never work as expected.
The scope of this task involves discussion with the CI team, and probably providing patches for them
Attachments
Gerrit Reviews
For Gerrit Dashboard: QTBUG-104898 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
541513,1 | WIP: Remove moc woraround as it blocks enabling deprecation warnings | dev | qt/qtdeclarative | Status: NEW | -2 | 0 |