2022-07-05 11:26:52 +00:00
|
|
|
# Copyright (C) 2022 The Qt Company Ltd.
|
2022-08-19 13:21:34 +00:00
|
|
|
# SPDX-License-Identifier: BSD-3-Clause
|
2022-07-05 11:26:52 +00:00
|
|
|
|
2019-11-12 13:01:48 +00:00
|
|
|
#####################################################################
|
|
|
|
|
## qget Binary:
|
|
|
|
|
#####################################################################
|
|
|
|
|
|
2020-09-22 08:16:58 +00:00
|
|
|
qt_internal_add_manual_test(qget
|
2019-11-12 13:01:48 +00:00
|
|
|
SOURCES
|
|
|
|
|
downloadmanager.cpp
|
|
|
|
|
qget.cpp qget.h
|
|
|
|
|
transferitem.cpp
|
Mark all of Qt as free of Q_FOREACH, except where it isn't
The density of Q_FOREACH uses in this and some other modules is still
extremely high, too high for anyone to tackle in a short amount of
time. Even if they're not concentrated in just a few TUs, we need to
make progress on a global QT_NO_FOREACH default, so grab the nettle
and stick to our strategy:
Mark the whole of Qt with QT_NO_FOREACH, to prevent new uses from
creeping in, and whitelist the affected TUs by #undef'ing
QT_NO_FOREACH locally, at the top of each file. For TUs that are part
of a larger executable, this requires these files to be compiled
separately, so add them to NO_PCH_SOURCES (which implies
NO_UNITY_BUILD_SOURCES, too).
In tst_qglobal.cpp and tst_qcollections.cpp change the comment on the
#undef QT_NO_FOREACH to indicate that these actually test the macro.
Task-number: QTBUG-115839
Change-Id: Iecc444eb7d43d7e4d037f6e155abe0e14a00a5d6
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
2023-08-07 15:59:46 +00:00
|
|
|
NO_PCH_SOURCES
|
|
|
|
|
downloadmanager.cpp # undef QT_NO_FOREACH
|
|
|
|
|
qget.cpp # undef QT_NO_FOREACH
|
2022-07-25 15:50:38 +00:00
|
|
|
LIBRARIES
|
2019-11-12 13:01:48 +00:00
|
|
|
Qt::Network
|
|
|
|
|
)
|
