From a81563afddb8b0f38fef51aafbe57b77437daf25 Mon Sep 17 00:00:00 2001
From: Daniel Teske <daniel.teske@digia.com>
Date: Wed, 17 Oct 2012 15:44:47 +0200
Subject: [PATCH] Qt4BuildConfiguration: Don't emit environmentChanged()

The BuildConfiguration already takes care of that on kit updates and I
can't see a reason to emit it for changing the build directory.

Change-Id: I58f13dbddf4d4c3f99b444de21c74326ee4ac182
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
---
 src/plugins/qt4projectmanager/qt4buildconfiguration.cpp | 2 --
 1 file changed, 2 deletions(-)

diff --git a/src/plugins/qt4projectmanager/qt4buildconfiguration.cpp b/src/plugins/qt4projectmanager/qt4buildconfiguration.cpp
index b5ce721d85a..02e8ad68e34 100644
--- a/src/plugins/qt4projectmanager/qt4buildconfiguration.cpp
+++ b/src/plugins/qt4projectmanager/qt4buildconfiguration.cpp
@@ -143,7 +143,6 @@ void Qt4BuildConfiguration::ctor()
 void Qt4BuildConfiguration::kitChanged()
 {
     emitProFileEvaluateNeeded();
-    emit environmentChanged();
     emitBuildDirectoryChanged();
 }
 
@@ -256,7 +255,6 @@ void Qt4BuildConfiguration::setShadowBuildAndDirectory(bool shadowBuild, const Q
     m_shadowBuild = toSet;
     m_buildDirectory = directoryToSet;
 
-    emit environmentChanged();
     emitBuildDirectoryChanged();
     emitProFileEvaluateNeeded();
 }