From 7ea6cee52533009799e025e6f66c5ff2cb907b23 Mon Sep 17 00:00:00 2001 From: Lars Knoll Date: Wed, 13 May 2020 15:35:52 +0200 Subject: Don't enable -headerclean by default even for developer builds The CI system can test this, but there's little reason to blow up every developers compile time by 30%. Change-Id: I7677b0411103fb1301ad087c884cc9bd22a5aee2 Reviewed-by: Alexandru Croitor --- configure.cmake | 2 +- configure.json | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/configure.cmake b/configure.cmake index d262882bb5..a3a8669d27 100644 --- a/configure.cmake +++ b/configure.cmake @@ -419,7 +419,7 @@ qt_feature("force_asserts" PUBLIC ) qt_feature("headersclean" LABEL "Check for clean headers" - AUTODETECT QT_FEATURE_developer_build + AUTODETECT OFF CONDITION NOT WASM ) qt_feature_config("headersclean" QMAKE_PRIVATE_CONFIG) diff --git a/configure.json b/configure.json index bb4813e308..6d1385dafe 100644 --- a/configure.json +++ b/configure.json @@ -832,7 +832,7 @@ }, "headersclean": { "label": "Check for clean headers", - "autoDetect": "features.developer-build", + "autoDetect": false, "condition": "!config.wasm", "output": [ "privateConfig" ] }, -- cgit v1.2.3