https://bugs.kde.org/show_bug.cgi?id=460450
--- Comment #5 from Igor Kushnir <igor...@gmail.com> --- KDevelop happily runs cmake-configure a second time when the user requests build, while automatic cmake-configure is running after a change to CMakeLists.txt. Preventing KDevelop from running multiple cmake-configure for the same project simultaneously is a good idea. However, the steps in this bug report don't lead to concurrent cmake-configure runs. So a different fix would be needed here. Possibly based on timestamps. I don't think taking external cmake-configure processes into account is particularly important here, because the user is unlikely to start a build in an external terminal and then immediately modify and save a cmake file. Seems to be much less likely than two close-by modifications of a cmake file without explicit build requests in an external terminal. -- You are receiving this mail because: You are watching all bug changes.
