Binaries :

Some Linux/UNIX OS vendors have kindly provided binary packages of KDevelop for some versions of their distribution, and in other cases community volunteers have done so. Some of these binary packages are available for free download from KDE's http or FTP mirrors.

KDevelop 3.5.5-0 (stable snapshots, RPM and deb, built by the kdevelop team) [2009-08-11]

Debian and (k)ubuntu users don't need to download the .debs and install them, just put:
deb http://ftp5.gwdg.de/pub/opensuse/repositories/home:/amilcarlucas/Debian_Etch/ ./
or
deb http://ftp5.gwdg.de/pub/opensuse/repositories/home:/amilcarlucas/xUbuntu_6.06/ ./
or
deb http://ftp5.gwdg.de/pub/opensuse/repositories/home:/amilcarlucas/xUbuntu_7.10/ ./
or
deb http://ftp5.gwdg.de/pub/opensuse/repositories/home:/amilcarlucas/xUbuntu_8.04/ ./
or
deb http://ftp5.gwdg.de/pub/opensuse/repositories/home:/amilcarlucas/xUbuntu_8.10/ ./
or
deb http://ftp5.gwdg.de/pub/opensuse/repositories/home:/amilcarlucas/xUbuntu_9.04/ ./
into your sources.list file. Then you can install the new KDevelop after updating the package list (i.e. run apt-get update and install with apt-get install kdevelop).

KDevelop 3.5.3 (older release) [2008-08-26]

GDB 6.8.50 [2008-06-23]

Sources for KDE >= 3.4 :

KDevelop 3.5.5-0 src.rpm [2009-08-11]

Or you could get the latest sources directly from KDevelop's SVN source repository.

1. Before continuing please check if your computer has the required software installed.


2. Uncompress the source file and change to the base directory:

   $ bunzip2 kdevelop-3.5.5.tar.bz2

   $ tar -xf kdevelop-3.5.5.tar

   $ cd kdevelop-3.5.5

4. In order to compile and install KDevelop on your system, type the commands (we assume you have bash shell) from below in the base directory.

   $ export KDEDIR=/where/your/kde3/is

   $ export QTDIR=/where/your/qt3/is

   $ export KDEVELOPDIR=/where/kdevelop/will/be/installed

   $ export KDEDIRS=$KDEVELOPDIR:$KDEDIR

   $ export LD_LIBRARY_PATH=$QTDIR/lib:$KDEDIR/lib:$LD_LIBRARY_PATH

   $ export LIBRARY_PATH=$QTDIR/lib:$KDEDIR/lib:$LIBRARY_PATH

   $ export PATH=$KDEVELOPDIR/bin:$QTDIR/bin:$KDEDIR/bin:$PATH

   Note: For obvious reasons you should edit the first three lines to match your configuration!
   On RPM based linux distributions, you can find the location of your Qt3 and KDE3 directories using the configuration program of your linux distribuition or simply issuing "rpm -ql qt3" and "rpm -ql kdebase3".
   If you are a gentoo user and want to use ctags then you need to issue:

   ln -sf /usr/bin/exuberant-ctags /usr/bin/ctags




5. The next step is to configure it, to find out more about all the available configure options invoke:

   $ ./configure --help

   Here is an example of a debug-compiled version:

   $ ./configure --enable-debug=full --prefix=$KDEVELOPDIR --with-kdelibsdoxy-dir=$KDEDIR/share/doc/HTML/en/kdelibs-apidocs

   Here is an example of a release-compiled version:

   $ ./configure --prefix=$KDEVELOPDIR --with-kdelibsdoxy-dir=$KDEDIR/share/doc/HTML/en/kdelibs-apidocs

   You can avoid compiling some KDevelop components that you do not need, for example, I use the following configure command:

   $ ./configure --enable-debug=full --prefix=$KDEVELOPDIR --with-kdelibsdoxy-dir=$KDEDIR/share/doc/HTML/en/kdelibs-apidocs --disable-ada --disable-bash --disable-fortran --disable-haskell --disable-java --disable-pascal --disable-perl --disable-php --disable-python --disable-ruby --disable-sql --disable-antproject --disable-genericproject --disable-scriptproject --disable-trollproject --disable-clearcase --disable-perforce --disable-subversion

6. Finaly you can build it and install it:

   $ make

   $ make install (as root, using for example the "su" command)

   If for some reason the make command fails you can force it to ignore errors by adding the -k option like this:

   $ make -k

   $ make -k install (as root)

   Depending on the error gravity you might end up with a working or non-working version of kdevelop. So do the "make -k install" at your own risk!!!.

You should report the bugs you find with the bug submition form. You should not report compilation errors to the bug database. For compilation errors use the mailing list instead.

• Versions
• User Manual
• TechNotes
• Wiki

• Changes
• SVN Branches & Compiling
• Join us!
• Website translation

• User Programs
• Sponsors
• Dev. Tools

• In the Press
• Awards
• Logos & Banners
• Splashscreens

• Bugs & wishes
• On-line chat
• Forum
• Mailinglist
• Guestbook
• Credits