You are right, this is a problem for the usual case of re-running CMake when the project configuration changes.
But in this use-case CMake would only be run once and then the IDE project would take over project configuration for the rest of the application lifetime. It also allows the use-case of temporarily doing simple project configuration through the IDE UI. -----Original Message----- From: Ben Boeckel [mailto:ben.boec...@kitware.com] Sent: 25. januar 2017 15:43 To: Bøe, Sebastian <sebastian....@nordicsemi.no> Cc: cmake-developers@cmake.org Subject: Re: [cmake-developers] Eclipse CDT Managed build On Wed, Jan 25, 2017 at 14:31:32 +0000, Bøe, Sebastian wrote: > I was wondering if anyone has given thought to if it is feasible to > have generator support for Eclipse CDT Managed builds? It would likely be possible, but I don't know of any work towards this goal. > My motivation for managed build's instead of external Makefile builds, > is that after CMake generation the project can be configured through > the IDE UI. Which is a useful property in an SDK context. This could be a problem though. Are the files that the IDE edits separate from the ones that CMake generates? If not, how would CMake know not to clobber the edited parts of the files it does generate? --Ben -- 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: http://public.kitware.com/mailman/listinfo/cmake-developers
