[CMake] [PATCH] kdevelop3 generator, 2nd version

[Andy Cedilnik]

Hi Alex,

I am not sure I understand this. I have KDevelop 3.0.4 and that one can
read the toplevel Project.kdevelop file properly. There is nothing in
the source.

The subproject kdevelop files should be treated separately, since they
are not included in the toplevel project.

So, the toplevel build/Project.kdevelop.filelist should have all files
that are necessary to build the project. We could play with groups to
name them based on the sub-project name. Sort of what Visual Studio
generator does.

On Tue, 2004-10-12 at 13:18, Alexander Neundorf wrote:
> I'd say 
>  
> source/Project.kdevelop.filelist 
> source/Project_sub.kdevelop.filelist 
> build/Project.kdevelop 
> build/sub/Project_sub.kdevelop 
>  
> Otherwise it won't work (see below). 


> Yes, as it is now in cvs it doesn't work. 
> I tried here with kdevelop 3.0.0 and KDE 3.2.1. 
> KDevelop only shows files with relative paths and these paths may not go 
> upwards (../something/). 
> By giving the project files everywhere the same name all kdevelop 
> projects use the same foo.kdevelop.filelist file, which is not optimal 
> I'd say and more important it doesn't work. 
> So, this will only work if the foo.kdevelop.filelist file is generated in 
> the top source directory (as it did in my patch). 

Maybe this feature appeared in 3.0.4, but as I said, here it works fine.
We can open files, edit them, build, etc.

The CMake.kdevelop projects in subdirectories should be removed and
maybe replaced with the actual project files.

 
-- 
				Andy Cedilnik
				Kitware Inc.