- Kdevelop is the next generation of IDE (integrated
develepmont environment) tools for the C/C++ programmer. It
is compatible with Gnome, as well as (obviously) standard K
applications. This product is very, very, good.
- The Kdevelop environment is Qt intensive, most of the
work revolves around this generic library from Norway.
Kdevelop provides c++ classes and widgets for both Qt and,
separately, kde applications. All donkey-work can be achieved
via wizards, and the wizards work!
- Separately, Kdevelop offers you the opportunity to write
your code using the emerging KDE2 (QT2) standards.
(multi-threading == KDE2).
- Using wizards, you can generate code for standard
terminal applications, up to and including Kwidgets,
- The documentation provided with this product is
outstanding. They deserve a medal. It is all available
in help screens and covers EVERYTHING.
- In addition, any package YOU write, is auto documented.
Kdevelop automatically generates html pages for all classes
you write, as well as a 'handbook' for you to fill in with
appropriate detail. The depth of detail and cross reference
links provided by the auto-document feature is staggeringly
- Step and debug is naturally available.
- Generating gui panels and dialogs is achieved by the
The version shipped with Caldera's e2.4 (version 1.0) is
slightly buggy, but highly useable. Two some upgrades are a
- Installing glimpse (a search engine)
- Upgrading to Kdevelop 1.1
- Installing the c++ reference library
1) The glimpse package is not supplied. Go to
The package is caldera friendly
2) A better revision.
Some minor, but irritating bugs were fixed on version 1.1
Unfortunately, the redhat and mandrake rpms of this newer
package are unfriendly. This is where you need to be:
Download the tarball
As usual, with most tarballs these days, this one compiles
'out of the box'
tar -zxvf kdevelop-1.1.tar.gz
BEFORE doing the last step, remove your current kdevelop rpm
(using kpackage, or rpm -e) if you installed it.
Note also, that during the 'configure' step it will complain
noisily if you do not have the STATIC qt libraries installed.
Specifically 'moc' dependencies. Make sure you have rpm
installed all relevant qt libraries before moving to kdevelop
as they are intertwined.
3) Installing c++ reference documentation
SInce I hardly know c++ (but a great deal about C), i found
this reference very handy. It merges into the existing Kdevelop
environment without you doing one thing further.
tar -zxvf c_cpp_reference-1.0.tar.gz