diff options
author | Friedrich W. H. Kossebau <kossebau@kde.org> | 2018-06-29 20:39:18 +0200 |
---|---|---|
committer | Friedrich W. H. Kossebau <kossebau@kde.org> | 2018-06-29 23:58:37 +0200 |
commit | 484d5f4ceea2b8d23c9a0d35f16077f7cabfbd27 (patch) | |
tree | 9e9bc5703e5f893e640c81a3bd3dc860ee3312b5 /docs/find-module | |
parent | 60cb4b74bce8bc0f65ea3dc2cd7966602dd50694 (diff) | |
download | extra-cmake-modules-484d5f4ceea2b8d23c9a0d35f16077f7cabfbd27.tar.gz extra-cmake-modules-484d5f4ceea2b8d23c9a0d35f16077f7cabfbd27.tar.bz2 |
Drop outdated QT_USE_FAST_OPERATOR_PLUS
Summary:
QT_USE_FAST_OPERATOR_PLUS has been deprecated in Qt 4.8, in favour of
QT_USE_QSTRINGBUILDER. The latter also covers QByteArray.
Qt5 headers still supports QT_USE_FAST_OPERATOR_PLUS (at least 5.11.1),
as subset of QT_USE_QSTRINGBUILDER as it was introduced in Qt4.8,
but not as documented build flag.
Given QT_USE_QSTRINGBUILDER is set here and thus triggers anything that
QT_USE_FAST_OPERATOR_PLUS would trigger in Qt code, removing it should
clean up the macro from undocumented features and thus reduce confusion.
No non-Qt is known at least in KDE repos which checks this build flag
otherwise, so no regression should be expected here as well.
Reviewers: vkrause
Reviewed By: vkrause
Subscribers: kde-frameworks-devel, kde-buildsystem
Tags: #frameworks, #build_system
Differential Revision: https://phabricator.kde.org/D13800
Diffstat (limited to 'docs/find-module')
0 files changed, 0 insertions, 0 deletions