diff options
| author | Jan Kundrát <jkt@kde.org> | 2016-09-14 23:51:14 +0200 |
|---|---|---|
| committer | Jani Heikkinen <jani.heikkinen@qt.io> | 2016-12-10 16:32:34 +0000 |
| commit | 74ac5b0f3489f9a08d083b6c9607c9d5c2d4afd2 (patch) | |
| tree | f8a4e9ae43356f56efde3644a186f6ba4d091d78 | |
| parent | 7ae27514e4a800eb0419879dc38cfdfce897ad60 (diff) | |
Remove unused check for private_tests
It turns out that qt_developer_build is never used anyway.
I did some git archeology and it looks like it was nuked when doing the
5.2 merge from upstream. The original purpose was apparently to control
-Werror, which is nowadays controlled by CONFIG -= production_build.
This actually fixes the build, as the QT_FOR_CONFIG += core-private which
would have been required for qtConfig(private_tests) is missing.
Task-number: QTBUG-55950
Change-Id: Iaaaad184b29b523ce4a4ed8afec2ac527d8f93e3
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>
Reviewed-by: Konstantin Tokarev <annulen@yandex.ru>
Reviewed-by: Jan Kundrát <jkt@kde.org>
| -rw-r--r-- | Tools/qmake/mkspecs/features/default_pre.prf | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/Tools/qmake/mkspecs/features/default_pre.prf b/Tools/qmake/mkspecs/features/default_pre.prf index 568e80a94..5c36e9313 100644 --- a/Tools/qmake/mkspecs/features/default_pre.prf +++ b/Tools/qmake/mkspecs/features/default_pre.prf @@ -62,10 +62,6 @@ win32-msvc*: MAKEFILE_NOOP_COMMAND = @echo >NUL scratchbox: PYTHON = python2.6 else: PYTHON = python -# We use private_tests to detect developer build, since the destdir will -# always be our webkit build dir. This might change as configure changes. -qtConfig(private_tests): CONFIG += qt_developer_build - # By default we enable "production build", and build-webkit, which is # used by bots and developers, will disable it, to enable warnings etc. CONFIG += production_build |