Seems like a pretty big issue though, if people have to open task manager every time they rethink what they're doing in CMake and what not.
Maybe someone has a workaround or something. And #1 might not be possible if CMake is monitoring a file instead of printing input to console & file......... On Sat, Dec 22, 2018 at 2:56 PM frodak17 <froda...@gmail.com> wrote: > > > On Sat, Dec 22, 2018 at 5:17 PM Person Withhats <personwithha...@gmail.com> > wrote: > >> >> 2) Pressing 'Stop' does not halt processes spun up by execute_process, >> CMake waits until they finish before exiting.....very aggrevating! >> >> > Looks like this would require a code change how the GUI works and the > internal way execute_process works. Now execute_process knows how to > cancel a process due to time out, but it didn't seem to check for anything > else. Essentially it looks like execute_process needs to be signaled by > the button press to cancel the process in addition to checking for > timeout. There are other internal interrupt flags that seem to be set when > the GUI stop button is pressed. Anyways this is what I noticed in the code > base. >
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
