KDevelop TechNotes Issues #1 and #2

I have started a series of KDevelop related articles. I call them "KDevelop TechNotes" and plan to publish all useful information about the IDE - tips and tricks, use cases, tutorials, etc. Everyone is welcome to share KDevelop knowledge by writing their own issues of technotes. I will be pleased to publish them on the project website.

The first issue should be a matter of no little interest to all free software developers. Read about KDevelop Assistant - an advanced API documentation viewer.

The second issue will tell you about rapid application development with KDevelop IDE using C++ language and Qt and/or KDE libraries. Do you know that KDevelop IDE offers integrated GUI design facilities? Do you know how to develop an application with a GUI in just two minutes? No? Learn more about that.


Good stuff, thanks a lot!

By LB at Fri, 2004/12/03 - 6:00am

Debugging with the KDevelop/gdb combo that comes with Debian unstable has been a complete no go for me so far. Last time I tried it a couple of months back I only got as far as stepping through the first lines of the main() of the skeleton program KDevelop itself creates. Once it came to the KApplication contructor it just stopped there and wouldn't go any further. It seemed like the problem was that gdb choked on shared libraries or something like that. Any ideas?

By would be KDevel... at Fri, 2004/12/03 - 6:00am

There are still some issues with the gdb interface, however [I'm not using Deb unstable] in general I have no particular problems debugging.
Have a look at the forum on or search/ask on the mailing list [].

By Ste at Fri, 2004/12/03 - 6:00am

It seems that you have stripped libraries with no debug symbols at all. I don't know much about debian maybe it provides libraries with debug symbols.

By Alexander Dymo at Fri, 2004/12/03 - 6:00am

This URL was helpful because it showed, right away, that only the subclassing method is viable with the current implementation. Some of us prefer to use .ui.h files, so this is both disappointing and exciting at once. I hope there's future plans to accommodate the .ui.h style.

By Dan Ostrowski at Fri, 2004/12/03 - 6:00am

ui.h files have a real drawback if you use the automake system (as it is used by default for any KDE application). If you modify the ui.h file, the build system will not notice the change and will not rebuild your executable...
So avoid it (at least in KDE CVS), unless you want to cause trouble to those using CVS versions and update from source frequently.


By Andras Mantia at Fri, 2004/12/03 - 6:00am

Designer integration in KDevelop was designed and implemented to be as convenient as former .ui.h method. Right now it should do the same you previously did with Qt Designer and .ui.h and even better (as Andras explained).
Trolltech don't use .ui.h approach in Qt4 so personally I'm not going to implement .ui.h like integration. But anyway, everybody is free to implement this ;)

By Alexander Dymo at Fri, 2004/12/03 - 6:00am

Is it possible yet to use KDevelop on a makefile-based app? I tried it a while ago and couldn't figure out how to override it's own automake-based orientation.

By Rob at Fri, 2004/12/03 - 6:00am

It seems that you tried 2.x version. With 3.x you should simply import your makefile-based project as "Custom makefiles project".
PS: welcome to #kdevelop at channel or use the web irc client:

By Alexander Dymo at Fri, 2004/12/03 - 6:00am

Thanks!! That's awesome. Didn't know Kdevelop could do that.

By Leo S at Sat, 2004/12/04 - 6:00am

Yeah.. 90% of what I write is just simple, one-off things that use a makefile. I'd like to take advantage of KDevelop's features but I just can't be bothered to use a full automake system for small projects so I do all my C/C++ programming in Kate instead.

By Leo S at Sat, 2004/12/04 - 6:00am

You should try QMake even for projects that do not use Qt library. It will simplify your life a lot. No need to write those makefiles. Maintaining one .pro file is _very_ simply.
You can create QMake projects with KDevelop and you can still use Kate if you want because no addional stuff instead of a short and simple .pro file is created. But KDevelop has a nice GUI to edit .pro files ;)

By Alexander Dymo at Sat, 2004/12/04 - 6:00am

Thanks for reminding me that I can run kdevassistant standalone, I think I saw it a while ago, but never remembered it.

It's a really great application.

By NoUseForAName at Sat, 2004/12/04 - 6:00am