diff options
| author | Claus Steuer <claus755@gmail.com> | 2017-06-19 17:29:35 +0200 |
|---|---|---|
| committer | Tobias Hunger <tobias.hunger@qt.io> | 2017-06-20 13:37:58 +0000 |
| commit | 8542ebcd5dd312aa3038d0b70c861dc05c71333a (patch) | |
| tree | fb476c0ac6b270e81190cdeadeb211c1505bcc00 /src/plugins/cmakeprojectmanager/cmakebuildstep.h | |
| parent | 523439d71b768874b2ac9613c151483f9961417f (diff) | |
CMake: Do not react to builds in the background
If an error occurs while persisting or updating the cmake state, the
build might continue for a while in the background.
CMakeBuildStep does not disconnect the Error/Run-Trigger when an
error is signaled by the CMakeBuildConfiguration. Instead it reports the
build as finished (with error). The BuildManager then disconnects the
output and runs the next item in the build queue (if any). However the
cmake step might still be alive and emits the dataAvailable signal which
then triggers the build process.
Task-number: QTCREATORBUG-18382
Change-Id: I956133fe8c6f7de58b9f842b231c70d24778b1e0
Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
Diffstat (limited to 'src/plugins/cmakeprojectmanager/cmakebuildstep.h')
| -rw-r--r-- | src/plugins/cmakeprojectmanager/cmakebuildstep.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/plugins/cmakeprojectmanager/cmakebuildstep.h b/src/plugins/cmakeprojectmanager/cmakebuildstep.h index 70d89c8783..08cee9a01c 100644 --- a/src/plugins/cmakeprojectmanager/cmakebuildstep.h +++ b/src/plugins/cmakeprojectmanager/cmakebuildstep.h @@ -104,6 +104,8 @@ private: void ctor(ProjectExplorer::BuildStepList *bsl); void runImpl(QFutureInterface<bool> &fi); + void handleCMakeError(QFutureInterface<bool> &fi, const QString& errorMessage); + void disconnectTriggers(); void handleBuildTargetChanges(); CMakeRunConfiguration *targetsActiveRunConfiguration() const; |