[cmake-developers] Eclipse CDT Managed build

[Bøe, Sebastian]

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.boeckel at kitware.com] 
Sent: 25. januar 2017 16:31
To: Bøe, Sebastian <Sebastian.Boe at nordicsemi.no>
Cc: cmake-developers at 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