Details
-
Bug
-
Resolution: Fixed
-
P3: Somewhat important
-
6.2.5, 6.3.1, 6.4.0 Beta1
-
None
-
Foundation Sprint 61, Foundation Sprint 62
Description
Note: currently I manually modify
function(qt_internal_library_deprecation_level result)
in qtbase/cmake/QtFlagHandlingHelpers.cmake to change the QT_DISABLE_DEPRECATED_BEFORE version.
Many methods are deprecated, starting from Qt 6.0. In many cases the declaration in header files is properly guarded, but the definition in cpp files is not.
Other problem is that in many places the code is still used, just wrapped into macros that silence the warning, for example:
QT_WARNING_PUSH QT_WARNING_DISABLE_DEPRECATED dbg << "QExposeEvent(" << static_cast<const QExposeEvent *>(e)->region() << ')'; QT_WARNING_POP
As a result, when we enable QT_DISABLE_DEPRECATED_BEFORE = 0x060000 or higher, we get multiple build errors.
Attachments
Issue Links
- blocks
-
QTBUG-104131 Make QT_INLINE_SINCE(maj, min) remove the out-of-line fall-back when deprecation point passes past (maj, min)
- Closed
- relates to
-
QTBUG-104858 QT_DISABLE_DEPRECATED_BEFORE is not propagated to unit-tests
- Closed
- resulted in
-
QTBUG-104909 Teach QWidgetWindow to handle QWindow::paintEvent
- Reported
-
QTBUG-104950 Fix deprecation warnings in QtDeclarative and compile with QT_DISABLE_DEPRECATED_BEFORE >= 0x060000
- Closed
-
QTBUG-104968 Fix deprecation warnings in Qt Tools and compile with QT_DISABLE_DEPRECATED_BEFORE=0x060000
- Closed
-
QTBUG-105126 Build QtBase with QT_DISABLE_DEPRECATED_BEFORE = current Qt version
- Closed