Broken single-file compile in "empty" (generic) project [PATCH]

Kuba Ober kuba at
Sat Jun 8 18:50:05 UTC 2002


The single-file compile in empty project types is broken. It doesn't call the 
gmake in proper working directory, and generally doesn't feel the clue about 
what it does.

I've noticed it when I switched from standard autoconf-based projects to 
playing with qmake-generated makefiles.

The attached patch makes it reasonably work (notably taking care of make 
options specified in project options, etc.), although I must look into the 
case when make would be run in project's root directory (say 
~/src/kdevelop-2.1) and the target would be somewhere deeper (say 
./kdevelop/kwrite/blah.cpp) -- then it will handle non-recursive make 
invocations allrighty (yep, there are some people who don't use recursive 

Cheers, Kuba Ober

PS. On monday or tuesday I'll have some more, revamped indent patches which 
hopefully will make indenting quite user-friendly (I use it constantly so I 
know ;-). This stuff seems generic enough to be ported into current kate's 
sources, and that will be my next step.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kdevelop-compile-file.patch
Type: text/x-diff
Size: 2578 bytes
Desc: not available
URL: <>

More information about the KDevelop-devel mailing list