[CMake] Bug? Broken header files in Visual C++ 2008 project

[Alexander Neundorf]

On Thursday 04 September 2008, Andreas Pakulat wrote:
> On 03.09.08 23:45:56, Alexander Neundorf wrote:
> > On Wednesday 03 September 2008, Andreas Pakulat wrote:
...
> > Ah, yes.
> > What would be cool would be if I could force kdevelop to reread its
> > project files (... after they have been regenerated by cmake).
> > Is this possible maybe via DCOP ?
>
> Let me check... The openProject() call is in fact available via dcop. Of
> course this is not a "silent" operation, i.e. the user will get asked if
> he wants to re-open the current project.
>
> I could add the needed functionality, but this won't show up in a stable
> release for quite some time.

I think I already thought about this some time ago.

So:
how does cmake find the correct kdevelop instance ?
$ dcopfind kdevelop-*
DCOPRef(kdevelop-4745,)

There could be multiple (usually probably not that many).
It could do for each of them:
$ dcop kdevelop-4745 KDevProject buildDirectory
/home/alex/src/CMake/build dir/CMake

And check whether the build directory is the same as CMAKE_BINARY_DIR. It 
could also check projectName, but I'm not sure this is necessary.
So if the build dir matches, which function to call then ?

$ dcop kdevelop-4745 KDevProject openProject /home/alex/src/CMake/build\ 
dir/CMake/ CMake.kdevelop

This pops up a dialog in kdevelop saying "This project doesn't contain any 
files yet. Populate it ?"

Why ? The filelist file is not empty.
Is there another dcop function I could call ?

...
> > <projectdirectory>
> > <projectmanagement>
> > <absoluteprojectpath>
> > <filelistdirectory>
> > <buildtool>
> > <builddir>
>
> I changed the builddir, by renaming it. Then re-run cmake -GKDevelop3
> and it didn't update the builddir entry in the .kdevelop file. After
> removing the CMake-related files, but leaving the kdevelop files the
> builddir is updated properly.

I'll have a look.

> BTW: This just told me why it is so bad that the cmake generator puts
> the kdevelop-files into the builddir. The builddir is often enough
> simply wiped out completely when you want to move it elsewhere or start
> from scratch - which means losing the project configuration. So at least
> the .kdevelop file should IMHO be generated in the sourcedir.

It's not a bug, it's a feature.
(seriuosly)
"No files must ever be created in the source dir" (could be read-only, or 
intended to be packaged as a source package, without any additional files, or 
different build dirs could use different IDE settings, etc.)

Alex