Clarify QT_DISABLE_DEPRECATED_UP_TO usage in static builds

Explicitly mention that in static builds Qt itself needs to be built with the same deprecation version as the user code. Fixes: QTBUG-125975 Pick-to: 6.8 6.7 6.5 Change-Id: I51b1e8b4ecd1731d3ff2320e758a52c5ef2c7cd9 Reviewed-by: Volker Hilsheimer <[email protected]> Reviewed-by: Edward Welbourne <[email protected]>
isolovev · Aug 25, 2024 · 47ff7d9 · 47ff7d9
1 parent b5d8552
commit 47ff7d9
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/src/corelib/global/qtdeprecationmarkers.qdoc b/src/corelib/global/qtdeprecationmarkers.qdoc
@@ -38,6 +38,12 @@
     make your binaries smaller by leaving out even the implementation of the
     deprecated APIs.
 
+    \note In order to avoid linker errors, the same deprecation level should be
+    used consistently in the entire binary. This means that in static builds
+    the Qt libraries should also be built with \c {QT_DISABLE_DEPRECATED_UP_TO}
+    set to the same version as in the user code. That is because in static
+    build the Qt libraries also become a part of the binary.
+
     \sa QT_DEPRECATED_WARNINGS, QT_DISABLE_DEPRECATED_UP_TO
 */