Support for custom projects

Ralf Nolden nolden at
Mon Dec 4 11:47:43 GMT 2000

Alexander Kuit wrote:
> On Montag,  4. Dezember 2000 11:49, you wrote:
> > Alexander Kuit wrote:
> > > This is a note on using kdevelop with custom (means: already existing,
> > > also non-KDE or -Qt) projects.
> >
> > Alexander,
> >
> > kdevelop 1.3 handles that pretty well for automake projects (requires
> > you to have a in all directories). Just go to "Project"
> > "Generate Projectfile".
> >
> > Ralf
> Our system is quite complex and historically grown. We don't use automake and
> I'm not in a possition to change this. Anyway, my approach should work
> without any assumption about the makefile structure, or am I wrong? My goal,
> and I suppose many others would agree with me, is to use kdevelop
> without assuming *anything*  about the existing stuff.

Well, then leave out the condition of an existing in the
directory hierarchy. Just edit the kimport script and you´re done ;)

The only way to get rid of a temptation is to yield to it. Oscar Wilde

Ralf Nolden

The KDevelop Project

nolden at
rnolden at

to unsubscribe from this list send an email to kdevelop-request at with the following body:
unsubscribe »your-email-address«

More information about the KDevelop mailing list