Last modified: 05 Feb 2002

Building KDirStat for KDE 2.x

Note:

If you are using the latest SuSE Linux, you may not have to build it at all; there usually is an RPM package you can use at the download area. See also the KDirStat home page.

Normal Build (no Treemap support)

Get the latest sources - either the tarball from the download area or via anonymous CVS from SourceForge.
Make sure you have a development system up and running.
You'll need at least:
- A C++ compiler
- Header files for the system libs
- X11 development environment (libs and header files)
- Qt 2.2 (or later) development environment
- KDE 2.x development environment
- maybe more. If you are unsure and you are running SuSE Linux, it might be a good idea to install the development system selection. You can also install this additionally on top of your running system - use YaST (the older text based version).

Please understand that I cannot and will not fix everybody's broken development systems any more - this had taken me quite some time with KDirStat 0.8x. Please make sure you can compile simple KDE programs like kless or kexample before contacting me about build problems.

Unpack the sources:
```
    tar xzvf kdirstat-1.8.5-beta.tgz
```
(or whatever version you downloaded)
Go to this directory:
```
    cd kdirstat-1.8.5-beta
```
Make sure I didn't accidentially include a config.cache file in the tarball - remove it to make sure. This is a neverending cause of trouble.
```
    rm -f config.cache
```
Let the configure script figure out where everything required is on your system.
Watch out for error messages and fix them before reporting errors!

On SuSE Linux systems, KDE 2.x is installed to /opt/kde2 which is a good idea if you want to keep some KDE 1.x programs around. So use that /opt/kde2 prefix for KDirStat, too - otherwise it will be installed to /opt/kde and clutter up a working KDE 1.x environment.
```
    ./configure --prefix=/opt/kde2
```
If you don't care about that or if you set up KDE 2.x in /opt/kde anyway, simply type
```
    ./configure
```
Compile everything:
```
    make
```
Again, watch out for error messages.
If everything worked out allright, become root and install the program and everything it needs:
```
    su
    make install
```
Don't do this if the previous step reported errors!

That's it.

Building with Treemap Support

Since June, 2001, KDirStat supports a fancy new way of displaying disk usage: Treemaps. This is still work in progress and to be considered experimental - use at your own risk.

Some time in August 2001, Alexander Rawass, the author of KDirStat's treemap part, decided to move a large part of this out to a separate project. He split off a generic part QTreeMap which became a separate project at SourceForge.

The problem with this decision is that from now on you need that separate QTreeMap lib (i.e. you need to download it from SourceForge and build and install it separately) - and you need versions of QTreeMap and its counterpart in KDirStat, KTreeMap, that are compatible with one another - which they more often than not are not, causing weird linker errors.

Because of that, I decided to make this part optional and exclude it by default.

Thus, if you wish to include that part, you need to explicitly request treemap support at configure time:

    ./configure --enable-treemaps

or (for SuSE Linux systems):

    ./configure --prefix=/opt/kde2 --enable-treemaps

All the rest is just like described above.

The --enable-treemaps option creates some symbolic links to the treemaps/ subdirectory, so you will need to remove them if you ever choose to build without treemaps. You can either remove those links manually or explicitly configure without treemaps:

    ./configure --disable-treemaps

or (for SuSE Linux systems):

    ./configure --prefix=/opt/kde2 --disable-treemaps

Troubleshooting

If you get weird linker errors, especially after enabling / disabling treemap support, try


	cd kdirstat
	./fix-linker-trouble
	cd ..
	make

This may or may not work. If it doesn't after enabling treemap support, most likely your versions of QTreeMap and KDirStat's KTreeMap are incompatible. In this case, disable treemap support.