[Cmake] [PATCH] kdevelop generator for cmake
Andy Cedilnik
andy.cedilnik at kitware.com
Wed Sep 22 17:43:11 EDT 2004
Hi Alex,
I am playing with KDevelop3 and I do not see foo.kdevelop.filelist:
These are files I see:
testofkdevelop.kdevelop
testofkdevelop.kdevelop.pcs
testofkdevelop.kdevses
I am not sure what the pcs file is (something binary), but kdevses has
recently open files etc, while kdevelop one has project information.
It does something funny though:
<kdevfileview>
<groups>
<group pattern="*.h" name="Header files" />
<group pattern="*.cpp" name="Source files" />
<hidenonprojectfiles>false</hidenonprojectfiles>
<hidenonlocation>false</hidenonlocation>
</groups>
<tree>
<hidepatterns>*.o,*.lo,CVS</hidepatterns>
<hidenonprojectfiles>false</hidenonprojectfiles>
</tree>
</kdevfileview>
So, it actually includes all .cpp and .h files.
Pretty wild.
Andy
On Wed, 2004-09-22 at 17:26, Alexander Neundorf wrote:
> Well, kdevelop needs two files, a foo.kdevelop and a
> foo.kdevelop.filelist. The first one contains the various settings and
> can be located anywhere. The second one simply lists all files belonging
> to the project and it *must* be located in a parent directory of the
> source files, i.e. somewhere at the root of the source tree.
> So if somebody chooses an out-of-source-build, foo.kdevelop, the Makefile
> and the objects will be generated out-of-source, but
> foo.kdevelop.filelist will be created in the source tree, there's no way
> around this, without chaging the kdevelop behaviour.
> For the location of the foo.kdevelop.filelist I wanted to use
> PROJECT_SOURCE_DIR, but this only makes sense if the CMakeLists.txt
> contains the PROJECT() call.
>
> Bye
> Alex
>
--
Andy Cedilnik
Kitware Inc.
More information about the CMake
mailing list