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

Kuba Ober kuba at
Sun Jun 9 19:27:04 UTC 2002

On sobota 08 czerwiec 2002 12:49 pm, Kuba Ober wrote:
> Hi,
> 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
> make).

Testing, anyone?

Myself, I believe this can get applied, because:
- previously the single-file compile didn't work at all on "empty" projects
- the normal project compiles aren't touched by the patch, so the 
functionality most people use is left alone

I'll also make another patch for build and rebuild along similar lines. 
Currently, build and rebuild complains about missing makefiles even when the 
makefiles are certainly there. I'll look into it and fix by mid-week.

Maybe I'll even put it up into bug database, but maybe then I won't if I have 
the patch up first.

Cheers, Kuba Ober

More information about the KDevelop-devel mailing list