[CMake] Avoid losing changes in Xcode when changing CMakeLists.txt

[Alexander Neundorf]

On Thursday 22 July 2010, Michael Wild wrote:
> On 22. Jul, 2010, at 15:57 , David Ojeda wrote:
> > Hello CMakers!
> >
> > I am coding with some teammates that use Xcode as their IDE. Everything
> > is working fine thanks to CMake, except for the following situation:
> >
> > 1. Developer X checkouts a project from svn and uses CMake to generate
> > their Xcode project
> > 2. Developer X succesfully compiles their executables and configures this
> > executables in the Xcode environment (for example, he changes its
> > arguments, library configurations for debugging, etc).
> > 3. Developer Y checkouts the same project from svn and changes
> > CMakeLists.txt (for example, he adds another library dependency or a new
> > source file).
> > 4. Developer Y commits its changes
> > 5. Developer X updates its project and must re-generate their Xcode
> > project. 6. PROBLEM: All changes made at step 2 were lost for Developer
> > X.
> >
> > Have any of you had this problem before? How can I maintain developer X's
> > settings?
> >
> > Thanks for your ideas!
> >
> > David.
>
> Well, tell X not to change anything in Xcode ;-) Either make the changes in
> the cache, or if otherwise not possible,
> modify the CMake code,  

which would mean either: when generating the new Xcode project file, merge the 
settings with the already existing one (of there are settings which can be 
changed by the user and which are not set at all by cmake), or, add some 
special cache variables to cmake which can be changed by the user and will be 
used by the Xcode generator to write these specific entries in the project 
file.

Alex