whytofly
/
qt6-bb10
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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.7 6.5
Change-Id: I51b1e8b4ecd1731d3ff2320e758a52c5ef2c7cd9
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
(cherry picked from commit 47ff7d99a06321559d7ab1682869732ea6e08359)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
bb10
Ivan Solovev 2024-08-21 14:13:07 +02:00 committed by Qt Cherry-pick Bot
parent 57f0085fec
commit a2b94167ab
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/corelib/global/qtdeprecationmarkers.qdoc
View File

@ -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
*/