From 843999d578cb9bd36a4411585b87fff7f8dba9b2 Mon Sep 17 00:00:00 2001 From: Christian Kandeler Date: Fri, 2 Jul 2021 10:30:23 +0200 Subject: [PATCH] ProjectExplorer: Properly handle project environment changes ... in the build configuration. We need to update the cache, so that the changes are propagated to run configurations. Fixes: QTCREATORBUG-25947 Change-Id: I1051df7dd03274acba1e66c3cbb9d3cb01552b4b Reviewed-by: hjk --- src/plugins/projectexplorer/buildconfiguration.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/plugins/projectexplorer/buildconfiguration.cpp b/src/plugins/projectexplorer/buildconfiguration.cpp index 63ba53c4fb1..6067d75f167 100644 --- a/src/plugins/projectexplorer/buildconfiguration.cpp +++ b/src/plugins/projectexplorer/buildconfiguration.cpp @@ -196,7 +196,7 @@ BuildConfiguration::BuildConfiguration(Target *target, Utils::Id id) connect(this, &BuildConfiguration::environmentChanged, this, &BuildConfiguration::emitBuildDirectoryChanged); connect(target->project(), &Project::environmentChanged, - this, &BuildConfiguration::environmentChanged); + this, &BuildConfiguration::updateCacheAndEmitEnvironmentChanged); // Many macroexpanders are based on the current project, so they may change the environment: connect(ProjectTree::instance(), &ProjectTree::currentProjectChanged, this, &BuildConfiguration::updateCacheAndEmitEnvironmentChanged);