To get the latest source code from one of the branches:

$ mkdir kdevelop

$ cd kdevelop

• command line for HEAD branch:
  

  $ svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdevelop/ kdevelop

• command line for KDE/3.5 branch:
  

  $ svn co svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kdevelop/ kdevelop

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


2. Get the sources for the KDE/3.5 branch like is explained above.


3. Initialize the build system:

   $ cd kdevelop

   $ make -f Makefile.cvs

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.

The easiest way to build KDevelop on MacOSX/X11 is to install all required packages via Fink or Darwin Ports and then compile KDevelop as described above using following configure command:

CXXFLAGS="-DMACOSX" ./configure --prefix=$KDEDIR --with-db-includedir=$BERKELEY_DB_INCLUDE_DIR --with-db-libdir=$BERKELEY_DB_LIBRARY_DIR --without-arts --with-extra-includes=$FINK_OR_DARWINPORTS_INCLUDE_DIR --with-extra-libs=$FINK_OR_DARWINPORTS_LIBRARY_DIR --with-qt-includes=$QTDIR --with-qt-libs=$QTDIR --disable-ada --disable-pascal

• -DMACOSX compiler flag and --disable-ada --disable-pascal are important because they enable MacOS specific code and disable two plugins that can not be compiled.
• Normally Fink installation directory is either /sw or /usr/local and DarwinPorts installation directory is /opt/local.
• Berkeley DB version 4.4 installed from the DarwinPorts will be in /opt/local/include/db44/ for includes and /opt/local/lib/db44/ for libraries.
• KDE from DarwinPorts will be installed into the same /opt/local directory.
• Qt directories for DarwinPorts installation in /opt/local would be /opt/local/include/qt3/ for includes and /opt/local/lib/qt3 for libraries.

1. To avoid typing in all the statements that set the necessary environment variables every time you update, you should set them in your .bashrc or .cshrc file.
   • If you use bash shell add the following lines:

     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

   • If you use tcsh add the following lines:

     setenv KDEDIR /where/your/kde3/is

     setenv QTDIR /where/your/qt3/is

     setenv KDEVELOPDIR /where/kdevelop/will/be/installed

     setenv KDEDIRS $KDEVELOPDIR:$KDEDIR

     setenv LD_LIBRARY_PATH $QTDIR/lib:$KDEDIR/lib:$LD_LIBRARY_PATH

     setenv LIBRARY_PATH $QTDIR/lib:$KDEDIR/lib:$LIBRARY_PATH

     setenv PATH $KDEVELOPDIR/bin:$QTDIR/bin:$KDEDIR/bin:$PATH

   Note: For obvious reasons you should edit the first three lines to match your configuration! :)



2. Go to the directory where you've put the kdevelop from SVN files and issue the update command:

   $ cd kdevelop

   $ svn up




3. The next step depends on the output of the previous command:
   • If you got something like:

     U /some_directory_path/Makefile.am

     You should do:

     $ make -f Makefile.cvs

     followed by the next ./configure step
   
   
   
   • If you got something like:

     P /some_directory_path/Makefile.am

     You should do:

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

     using the ./configure options that you used the first time you compiled it.



4. Compile kdevelop and install it:

   $ make

   $ make install (as root)

   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!!!. Any way these errors usually go away after a couple of hours so you might want to try an update again later before the dangerous :) make install command.

$ kdevelop

All you have to do to keep it up to date is to repeat these steps whenever someone on the kdevelop-devel mailing list fixes a bug. So you're strongly encouraged to join this mailing list.

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.

You can take a look at the bugs in the bug database.

• 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