From fc4e2028210477196364d76e4121612ea760437a Mon Sep 17 00:00:00 2001 From: Christian Kandeler Date: Tue, 23 Apr 2019 17:49:42 +0200 Subject: [PATCH] CMakeProjectManager: Fix deployment data setup In 73b1a765f3, we did not consider that the order of the code mattered, so we overwrote user-provided deployment information with guessed locations. Fixes: QTCREATORBUG-22184 Change-Id: Ied3a7436829e8b857c32e9364508a33414927c99 Reviewed-by: hjk --- src/plugins/cmakeprojectmanager/cmakebuildconfiguration.cpp | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/plugins/cmakeprojectmanager/cmakebuildconfiguration.cpp b/src/plugins/cmakeprojectmanager/cmakebuildconfiguration.cpp index b518888d50b..1deb85b1d16 100644 --- a/src/plugins/cmakeprojectmanager/cmakebuildconfiguration.cpp +++ b/src/plugins/cmakeprojectmanager/cmakebuildconfiguration.cpp @@ -204,7 +204,8 @@ DeploymentData CMakeBuildConfiguration::deploymentData() const for (const CMakeBuildTarget &ct : m_buildTargets) { if (ct.targetType == ExecutableType || ct.targetType == DynamicLibraryType) { - if (!ct.executable.isEmpty()) { + if (!ct.executable.isEmpty() + && !result.deployableForLocalFile(ct.executable.toString()).isValid()) { result.addFile(ct.executable.toString(), deploymentPrefix + buildDir.relativeFilePath(ct.executable.toFileInfo().dir().path()), DeployableFile::TypeExecutable);