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

[Kuba Ober]

On niedziela 09 czerwiec 2002 03:17 pm, falk.brettschneider at gmx.de wrote:
> Hi!
>
> Kuba Ober wrote:
> >Testing, anyone?
> >
> >
> >
> >Myself, I believe this can get applied, because:
> >- previously the single-file compile didn't work at all on "empty"
> > projects
>
> What do you mean with "empty" project? Do you mean "Custom" projects?
> Please, have a look in the AppWizard list.

other -> custom (to me it's like empty, i.e. not automake managed, sorry for 
confusion)

> >- 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 don't understand what you mean. Please, explain more in detail. Build
> and Rebuild works well here, even with Custom projects.

I doubt that it really works. That's how I can reproduce it:
(running kdevelop 2.1)
- start kdevelop (FRESH START, DO NOT RUN ANY COMPILES!!!)
- create a new project of the type that is the last entry in the appwizard 
(other -> custom) [I use polish localization, dunno about exact english 
wording of it].
- create a single class in the source subdirectory (say if the project is in 
./abc, then make the class using class wizard in ./abc/abc - that's where 
you'd normally make it, just to make things clear)
- optionally prepare a makefile for it (note that it's not needed that much, 
since gmake normally has internal rules for c++ files, so even w/o a Makefile 
it should always work).
- look what transpires when you hit "compile file" button. You'll get gmake 
complaining about being unable to find rule to make "yourfile.o".

Other than that, no make options are passed to make from project options 
dialog. The patch fixes that too.

Note that the code that is supposed to do this stuff doesn't even set the 
current working directory for make correcly.

Trying this after some stuff has been correctly built may give false 
impression that it works, since after compiles on full (ie. automake managed) 
projects, kdevelop changes current working directory. Sometimes it is changed 
to something that may enable make to work. Try this on a freshly started 
kdevelop.

> 17th June is cvs-tag day. We should stop committing some days before
> that date. To give people the chance to verify the latest commits. I'd
> say Wednesday is the last day open for bugfix commits. OK? The last days
> until the 17th should be used for testing our patches and (hopefully
> not) for emergency fixes of our own bugfixes. :-)

Got it. Is this date related somehow to kde 2.0.2 release date?

Cheers, Kuba Ober