[Cmake] [PATCH] kdevelop generator for cmake
Alexander Neundorf
a.neundorf-work at gmx.net
Wed Sep 22 17:26:02 EDT 2004
Hi Bill,
> PROJECT_SOURCE_DIR is always set, so there is no need to add the
check.
> However, that brings up another point. Are you writing files in the
> source tree?
> CMake should only be writing files into the binary tree. The only time
> anything should be written into the source tree is when the an
> in-source build is done and the binary directory is the same as the
> source.
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
--
GMX ProMail mit bestem Virenschutz http://www.gmx.net/de/go/mail
+++ Empfehlung der Redaktion +++ Internet Professionell 10/04 +++
More information about the CMake
mailing list