[CMake] [PATCH] kdevelop3 generator, 2nd version
Andy Cedilnik
andy.cedilnik at kitware.com
Tue Oct 12 17:25:16 EDT 2004
Hi Alex,
On Tue, 2004-10-12 at 17:18, Alexander Neundorf wrote:
> Yes. I just installed kdevelop 3.1.1 (the announcement was about 5
> minutes old when I downloaded it) and compiled it, still the same
> behaviour.
This is weird. I have whatever came with Debian and it works fine. Look
at the wiki.
> > I suppose this means we may have to go back to polluting the source
> > tree.
> > One other option, since kdevelop only works on unix, would be to
> > create a mirror tree with symlinks from the binary tree into the
> > source tree for out of source builds.
>
> You mean a symlink for each and every source file ?
> Hmm, not really a nice "solution"...
We could have a symlink of the whole source tree. So there would be
symlink src pointing to /.../wherever/your/source/is
> > How does one do an out of source build with kdevlop right now?
> > I am guessing you can't. Perhaps we should be lobbing the kdevlop
> > folks to add the feature of having a separate source tree from the
> > build tree, and having the project files live in the build tree.
>
> Yes. But this will take some time. Probably it will mean I have to send a
> patch.
> For the meantime it would be nice if the project files would be created
> as in my patch: the filelist file in the source dir, the project names
> built out of the project name and the subdirectory.
> Works well for me with a quite sophisticated cmake setup (the ecos stuff
> I posted some weeks ago).
The original patch produced lots of warnings on simple project like
CMake itself. You required PROJECT command in every directory if I
understand. Also, you require sources in the subdirectory of sources,
which means you cannot generate sources in the binary tree.
I will see how responsive KDevelop people are.
Andy
More information about the CMake
mailing list