Not modifying the CMakeListst.txt is acceptable for this use-case. But not being able to share, or relocate, the build tree is a problem.
Would support for relocatable build trees need major changes throughout CMake, or is this primarily a property of the generator? -----Original Message----- From: Ben Boeckel [mailto:ben.boec...@kitware.com] Sent: 25. januar 2017 16:31 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:51:26 +0000, Bøe, Sebastian wrote: > 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. CMake does not generally create relocatable build trees, so you cannot commit the generated files. That means that unless the CMakeLists.txt are never going to be changed (including via VCS branch changes), CMake may rerun on its own and clobber the changes since everyone will need to run it on their own once. --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
