# Installation of Krusader on KDE4.x

## Requirements

In order to successfully use the most recent &krusader;, you need &kde;libs >= 4.x

Required &kde; version:

- &krusader; v1.01: &kde; 2

- &krusader; v1.02 - 1.40: &kde; 3.0 - &kde; 3.2

- &krusader; 1.40: prefers &kde; 3.2 (otherwise all features will not be available)

- &krusader; v1.50 - v1.51: &kde; 3.2 - &kde; 3.3 (Konfigurator crash on &kde; 3.4)

- &krusader; v1.60.0 - v1.70.0: &kde; 3.3 - &kde; 3.5

- &krusader; 1.70.x: prefers &kde; >= 3.4 (otherwise all features will not be available)

- &krusader; 1.80.0: &kde; 3.4 - &kde; 3.5

- &krusader; 1.90.0: &kde; 3.2 - &kde; 3.5

- &krusader; v2.x.x: &kde; 4.x

NOTE: for installation instructions for &krusader;-1.x for &kde; 2 click here.

Platforms:

- All POSIX (&Linux;/BSD/&UNIX;-like OSes), &Solaris;

- All BSD Platforms (FreeBSD/NetBSD/OpenBSD/&MacOS;)

- &Windows; XP and Vista

In order to handle archives, checksums and other utilities they must be configured in our configuration tool. When running &krusader; for the first time the available utilities will be autodetected, and a report will be shown in the first lanch wizard. Afterwards additional utilities can be added/removed/changed.

A package of popular (un)packers, &krusader; itself and add-ons can be found on the &krusader; downloadpage.

For more requirements, see below. Have a look at the FAQ section as well.

## Obtaining &krusader;

The latest information about &krusader; can be found on the Krusader website .

### &krusader; Downloads

It is recommended to use the &krusader; package that is provided by your distribution. Distrowatch.com is a great resource to check the availability. If your distribution does not offer &krusader;, please contact the creators of your distribution and ask them to provide a &krusader; package

The latest version, as well as the older versions, can be found on the &krusader; downloadpage and on the Sourceforge mirrors. It contains the source tarballs, RPM and DEB packages to whatever distro the &krusader;-Krew is using and packages build by &krusader; users and third parties.

Distributions who provide &krusader;:

- &SuSE;

- Fedora via `# yum install krusader` will do the job, thanks to Marcin Garski. &RedHat; RPM packages can usually found on the &krusader; downloadpage or at dag.wieers.com and Dries Verachtert RPM Repository .

- Debian, on our &krusader; downloadpage you might find more recent DEB packages. Note: usually Debian packages work also on distributions that are "based on Debian", and some of these provide their own (incompatible) packages. Ubuntu/Kubuntu, Linspire/Freespire, Knoppix 4.x DVD, Kanotix, etc.

- Mandriva via the contrib repository `# urpmi krusader` will do the job, Gentoo, Yoper.

- Arch Linux, Frugalware Linux, PCLinuxOS, altlinux.

- FreeBSD, the port is maintained by Heiner Eichmann.

- NetBSD, Lunar Linux ,Ark Linux, OpenLX, Source Mage,CCux Linux, ROCK Linux.

- Even more distributions can be found with Distrowatch.com.

Use the installation tools included in your distro to install the &krusader; package. You might need an internet connection if &krusader; is not included on the &CD; or DVD. There are probably other distributions which include &krusader;. If you know of one, please send feedback so that we can include it on the distrolist.

Others

- Slackware tgz binaries can usually be found on the &krusader; downloadpage. You can also use Portpkg that contains a &krusader; SlackBuild, `# portpkg krusader` will do the job.

- There is a &MacOS;-X port with the help of fink , the port is maintained by Catalin Hritcu.

Search engines

- You can also find packages on &Linux; software archives such as freshmeat.net or KDE-APPS.org .

- If you can notfind a package for your distribution, we recommend searching for it with rpmfind, rpmpbone or rpmseek.

If you enjoy using &krusader;, we would appreciate it if you went to one of these sites and rated it.

If you still can not find a package, follow the installation procedure on how to compile &krusader; from source. This very thorough HowTo describes the process in such detail that even newcomers should not have any problems.

### Version Scheme

A new version scheme has been used since &krusader;-1.60.0

- First digit - the major version

- Second digit(s) - percentage of features completed for this major version

- Third digit(s) - bugfixes.

In essence, releasing &krusader;-1.60.0 means that we believe that &krusader; is about 60% done with all the features we had scheduled for the 1.x.x series. Series 2.x.x will be &kde; 4.x releases. Hopefully, it is easy to understand.

### Stable Version

`krusader-x.xx.tar.gz`

&krusader; is released under the &GNU; General Public License (GPL). This means that THE PROGRAM IS PROVIDED "AS IS" WITH NO WARRANTY OF ANY KIND, even when it is marked as a stable release.

### Development Version (beta release)

`krusader-x.xx-betax.tar.gz`

Before every stable release we release at least one development version in order to hunt down the bugs.

These releases are beta releases and will probably contain some bugs.

If you are using a development or SVN version, it is possible that the latest new features are not yet in the "The Krusader Handbook". Please read the Changelog file online or in the &krusader; sources to find out more about the new features. For a brief description, please read the SVNNEWS file online or in the &krusader; sources. User feedback and Bug reports are always welcome!

The beta release has 3 goals:

- Apply a feature-freeze until the stable is released, only bugs will be fixed. New features have to wait until the stable is released.

- Obtain feedback from &krusader; users so that we can fix the bugs.

- Give translators time to update the translations for the coming stable. Please read the i18n page.

### Subversion

Subversion is used for our sourcecode repository. It is also possible to Browse the Subversion Repository.

Currently, there are four module options:

- krusader_kde2: the &kde;2 branch, stable but it is basically v1.01 and there are no planned changes

- krusader_kde3: the &kde;3 branch, stable but it is basically v1.90.0 and there are no planned changes

- krusader_kde4: the &kde;4 branch that we currently use

- trunc: the &kde;4 the development version

To check out the latest &krusader; 1.x for &kde; 3 from SVN:

    $ svn co https://krusader.svn.sourceforge.net/svnroot/krusader/branches/krusader_kde3/

To check out the latest &krusader; 2.x for &kde; 4 from SVN:

    $ svn co https://krusader.svn.sourceforge.net/svnroot/krusader/branches/krusader_kde4/

To check out the latest developement &krusader; 2.x for &kde; 4 from SVN:

    $ svn co http://krusader.svn.sourceforge.net/svnroot/krusader/trunk/krusader_kde4

### Older Releases

If you are looking for older releases we recommend the Sourceforge mirrors, available from our project page.

## Krusader installation instructions on KDE4.x

Please read the `INSTALL` file of the Krusader sources, it contains all latest installation instructions.

From version &krusader;-2.0.0 and higher is &kde;-4 only.

At moment of writing &krusader;-2.0.0 is still under development, though it works :)

"krusader_kde4.tar.gz" is the supposed name of the krusader tarball (it will be probably a different one ;)

You can download the latest available krusader-2.x from SVN.

### Krusader dependencies

The next packages are needed to run the Krusader binary.

- c libraries

- kdelibs5 (KDE4 core libraries and binaries for all KDE4 applications)

- libkjsembed1 (Embedded JavaScript library) (for the the optional Javascripting function in Krusader)

### Suggested packages

These packages are optional but they will make Krusader much more powerful and useful.

The next packages are the names that Debian/Ubuntu uses, other Linux distros will probably use similar names.

- arj: archiver for .arj files

- ark: graphical archiving tool for KDE

- bzip2: high-quality block-sorting file compressor - utilities

- cpio: GNU cpio -- a program to manage archives of files

- kdebase-bin: core binaries for the KDE base module

- kdebase-bin: core binaries for the KDE base module

- kdiff3: compares and merges 2 or 3 files or directories

- OR kompare: a KDE GUI for viewing differences between files

- OR xxdiff: a graphical file and directories comparison and merge tool

- khexedit: KDE hex editor

- kmail: KDE Email client

- khexedit: KDE hex editor

- konsole: X terminal emulator for KDE

- krename: Powerful batch renamer for KDE

- lha: lzh archiver

- md5deep: versatile file checksum creator and verifier

- cfv: versatile file checksum creator and verifier

- p7zip: 7zr file archiver with high compression ratio

- rpm: Red Hat package manager

- unace: extract, test and view .ace archives

- unrar: Unarchiver for .rar files (non-free version)

- OR unrar-free: Unarchiver for .rar files

- OR rar: Archiver for .rar files

- unzip: De-archiver for .zip files

- zip: Archiver for .zip files

### Compilation requirements

The next packages are needed for compiling Krusader, if you only run a Krusader binary you don't need these packages.

- gcc (The GNU C compiler)

- g++ (The GNU C++ compiler)

- cmake (A cross-platform, open-source make system)

- zlib1g-dev: (library for implementing the deflate compression method found in gzip and PKZIP)

- gettext (contains msgfmt)

- kdelibs5-dev (installs many development libraries for KDE4)

- libphonon-dev (libphonon-dev cross-platform multimedia framework development)

## Installing on Linux and BSD platforms

Please read the `INSTALL` file of the Krusader sources, it contains all latest installation instructions.

`-DQT_INCLUDES=/usr/share/qt4/include` is the location of the &Qt;4 includes

`-DCMAKE_INSTALL_PREFIX=/usr/` is the location where Krusader will be installed with the make command.

An other example is: `-DCMAKE_INSTALL_PRFIX=/opt/krusader` to install the compiled Krusader in an other directory to not overwrite the Krusader version installed by your package manager.

          $ tar -xzvf krusader_kde4.tar.gz
          $ cd krusader_kde4
          $ cmake -DCMAKE_INSTALL_PREFIX=/usr/ -DQT_INCLUDES=/usr/share/qt4/include
          $ make
          $ sudo make install

Uninstall

          $ su -c "make uninstall"

## Installing on the &MacOS;-X platform

Please read the `INSTALL` file of the Krusader sources, it contains all latest installation instructions.

With &kde;-4 Krusader runs natively on &MacOS;-X, using it's Aqua user interface (No more X11 needed!).

In the near future (on moment of writing) with `MacPorts` installing Krusader should become `very easy!`

          $ sudo port install krusader

## Installing on the &Windows; platform

Please read the `INSTALL` file of the Krusader sources, it contains all latest installation instructions.

Tested on &Windows; XP, not yet tested on &Windows; Vista but it should work.

With Krusader-2.0.0 it's the first time that Krusader compiles on &Windows;, some work needs to be done to make Krusader more usable on the &Windows; platform. All feedback is welcome!

Krusader can be compiled and installed on &Windows; with the Win-KDE installer. See also windows.kde.org for more information.

## Starting &krusader;

Type ``krusader`` (lower case) at a command prompt. You can create shortcut on your desktop or create an entry in the (&kde;) menu. Read the previous page and the FAQ if &krusader; doesn't start.

When &krusader; is started from the command line, various options can be specified to modify its behavior.

        	$ krusader
        	WARNING: Mt.Man: Born, looking around to get familiar. foo

Do not worry about the messages you get in the &konsole;. These messages are log messages that can be used for debugging &krusader;.

You can also use &Alt; F2 to open the Run Command dialog box, type ``krusader`` (lower case) and press &Enter; or click on the Run button.

If &krusader; is installed by an RPM or DEB package then usually &krusader; can be started from the &kmenu;. e.g. on &Mandrake;-&Linux; 10.0 click on the &kicon; button and choose Applications File tools &krusader; .

### Command-line options:

`--left` <path>

  start left panel at <path>

`--right` <path>

  start right panel at <path>

`--left` <path1>,<path2>,<path3>

  start left panel at <path1>,<path2>,<path3>, with tabs.

`--profile` <panel-profile>

  load a panel-profile on startup (this overrides the default startup profile).

Examples:

    $ krusader --left=<path> --right=<path>

    $ krusader --left=/mnt/cdrom --right=ftp://downloads@myserver.net

    $ krusader --left=<path1>,<path2> --right=<path1>,<path2>,<path3>

    $ krusader--profile <panel-profile>

    $ krusader --profile ftp-managment

The standard &Qt; and &kde; command-line options are available, and can be listed by entering ``krusader` `--help`` .

### Other command-line options:

`--help-qt`

  List Qt-specific options

`--help-kde`

  List KDE-specific options

`--help-all`

  List all options

`--author`

  Show the authors names

`-v,--version`

  Show the version number

`--license`

  Show license information

## Configuring &krusader;

When you run &krusader; for the first time, the &krusader; configuration module Konfigurator will show up and allow you to configure &krusader; as well as detect installed packers and tools. You can always run Konfigurator again from the Settings menu.

## Making &krusader; the default file manager

To make &krusader; the default file manager in Gnome, click here for more information.

To make &krusader; the default file manager in &kde;, click here for more information.

# Installation on KDE3.x

## Compiling and Installing Krusader-1.x on KDE3.x

### Compiling &krusader;. What now?

Check the environment variables `KDEDIR` - `QTDIR`.

To compile and install &krusader; on your system, type the following in the base directory of the &krusader; package:

          $ ./configure
          $ make
          $ su -c 'make install'

If you install a CVS or beta version and if &krusader; was previously installed on your computer, then you should delete the `krusaderui.rc` file in your home directory to activate the new menu entries $ ``rm` `~/.kde/share/apps/krusader/krusaderui.rc`` , click here for more info.

Since &krusader; uses `autoconf` and `automake` you should have no trouble compiling it. If you run into problems, read the detailed installation instructions below.

### Quickstart Installation Tutorial

#### Debian

These instructions should work as well on Debian based distributions like: Ubuntu, Kubuntu, Linspire, Kanotix, ...

Add the next lines in the `~/.bashrc` configuration file

    export QTDIR=/usr
    export KDEDIR=/usr
    export export KDEDIRS=/opt/krusader:/usr

Install the build dependencies for &krusader;

    # apt-get build-dep krusader

Download the &krusader; sourcecode, unpack and enter the `krusader_kde3` directory.

The next command will create `./configure`

    $ make -f Makefile.cvs

NOTE: you might need to upgrade `automake` and/or `autoconf`, if an error message appears.

Install &krusader; in the `/opt` directory to not overwrite the official Debian binary `/usr/bin/krusader`, so that `krusader` will run the official Debian package and `/opt/bin/krusader` runs the compiled version. It's recommended to use enable the full debug, so that you can possible problems at us. Run configure.

    $ ./configure --prefix=/opt/krusader --enable-debug=full

Compile &krusader;

    $ make

Install Krusader

    $ su -c "make install"

`/opt/bin/krusader` runs the compiled &krusader; version.

#### SuSE

Install the build dependencies for &krusader;

Download the &krusader; sourcecode, unpack and enter the `krusader_kde3` directory. Now you can compile and install &krusader;

    $ make -f Makefile.cvs
    $ ./configure --prefix=/opt/krusader --enable-debug=full
    $ make
    $ su -c "make install"

#### For other Linuxes

Ofcource it's impossible to cover all Linuxes, but here are the general installation instructions.

Usually `./configure --prefix=/usr` should be used, though options like `/opt/krusader` are usually better so that you don't overwrite files that are installed by your package managment system. Please don't use the `/usr/local` directory as it simply won't work.

Install the build dependencies for &krusader;

Download the &krusader; sourcecode, unpack and enter the `krusader_kde3` directory. Now you can compile and install &krusader;

    $ make -f Makefile.cvs
    $ ./configure --prefix=/usr
    $ make
    $ su -c "make install"

### Detailed Installation Tutorial for Krusader on KDE3.

The next section will explain how to install &krusader; step by step. Questions about the installation process have been asked many times and especially users new to &Linux; often have problems compiling software from source. Therefore, we are trying to keep the explanations as detailed as possible even if they are mostly not &krusader; specific. Experienced users may easily skip most of the steps.

Unfortunately, because not all &Linux; distributions follow the Filesystem Hierarchy Standard (FHS) it is impossible to write a tutorial that would cover all circumstances. However, these guidelines will help you in the right direction.

If you encountered problems, please read first this installation procedure and the FAQ. If the problem persists, use the help request to ask for help.

1. Install all packages and libraries that are needed for the compilation, please read the FAQ.

   If you install Kdevelop, (almost) everything that you need to compile &krusader; will be installed on your computer. However, if you are not a developer, please follow the instructions and do not use Kdevelop to compile &krusader;.

2. Open your favourite terminal emulator (e.g. &konsole;).

3. We recommend you create a separate directory to keep all the sources you compile in. This way you will have a better overview of the installed programs and it will be easier to uninstall them later.

       $ mkdir ~/source

   The chosen directory is just an example, any other will work.

4. Copy the sources to the `~/source` directory and unpack them.

       $ cp /"your_dir" /krusader-x.xx.tar.gz ~/source

       $ cd ~/source

       $ tar -xzvf krusader-x.xx.tar.gz

5. Optional step: if you wish you can delete the tarball at this point as it is no longer needed.

       $ rm krusader-x.xx.tar.gz

6. Change to the directory containing the sources.

       $ cd krusader-x.xx

7. Check the environment variables `QTDIR`and `KDEDIR`. &krusader;'s `./configure` script needs to know where the &Qt; and &kde; directories are.

   `QTDIR`: <path to your Qt installation> e.g. `/usr/lib/qt3` or `/usr/qt3`

   `KDEDIR`: <path to your KDE installation> e.g. `/usr` or `/opt/kde3`

   Normally your distribution will set them for you, but experience has shown that some do not. You can easily check the values with the `echo` command.

       $ echo $QTDIR/usr/lib/qt3
                         $ echo $KDEDIR/usr

   If both commands give an output, the enviroment variables are set (the above example are the settings of Mandriva-&Linux;). In case you receive empty lines, the variables are not set and you have to set them manually. If you do not know what to set the variables to, or if you want to check if the variables are correctly set, ask your distributor or use the `find` command.

       $ find /usr /opt -name qtconfig -type f 2>/dev/null
       /usr/lib/qt3/bin/qtconfig
       $ find /usr /opt -name kdeinit -type f 2>/dev/null
       /usr/bin/kdeinit

   In this case `/usr/lib/qt3` is your `QTDIR` and `/usr` is your `KDEDIR`. The installed binaries will go to `/usr/bin`. Now we will set the enviroment variables with the `export` command.

       $ export QTDIR=<replace with your QTDIR>

       $ export KDEDIR=<replace with your KDEDIR>

   These enviroment variables are only set for the lifetime of your current shell. When you close your terminal and open a new one they will be gone. Assuming &krusader; is not the only &Qt;/&kde; program you want to compile, we recommend to make these settings permanent (e.g. append both export commands to your `/etc/profile`) file.

   If you can notdetermine your KDEDIR, `kde-config --prefix` might help you.

8. If you have downloaded a stable version `"krusader-x.xx.tar.gz"` or a beta version `"krusader-x.xx-betax.tar.gz"`, you can skip this step. In this case the `./configure` script is provided.

   If you have downloaded a CVS build or nightly tarball `"krusader-cvs-yyyy-mm-dd.tar.gz"`", you will have to run the following command to create the `./configure` script:

       $ make -fMakefile.cvs

   If everything is OK you will see the following output on your screen:

       $ make -f Makefile.cvs
       This Makefile is only for the CVS repository
       This will be deleted before making the distribution
       *** Creating acinclude.m4
       *** Creating list of subdirectories
       *** Creating configure.in
       *** Creating aclocal.m4
       *** Creating configure
       *** Creating config.h template
       *** Creating Makefile templates
       *** Postprocessing Makefile templates
       *** Creating date/time stamp
       *** Finished
       Don't forget to run ./configure
       If you haven't done so in a while, run ./configure --help
       $

   You will need to have autoconf 2.52, 2.53 or 2.54 and automake 1.6 (or higher) to run the `make -f Makefile.cvs` command

   If you encounter problems with this command click here. &krusader; provides two nightly builds (snapshots) one with a `./configure` script and one without.

9. Your &Linux; distro &krusader; RPM or DEB package will normally install &krusader; in the `KDEDIR/bin` directory. According to the Filesystem Hierarchy Standard (FHS), any user installed files go to the `/usr/local` directory. If you wish &krusader; to be installed in another directory, it can be determed with the prefix option. If you do not have root access, `/home/YOUR_USERNAME/.kde` is probably a good choice.

       foo

       Krusader Project:
       -----------------
       Source code location: .
       C Compiler:           gcc
       C Compiler flags:     -ansi -W -Wall -pedantic -Wchar-subscripts -Wshadow -Wpointer-arith
       -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -O2
       -Wformat-security -Wmissing-format-attribute
       C++ Compiler:         g++
       prefix:               /usr/local
       kde_libraries:        /usr/include
       kde_includes:         /usr/lib
       kde_locale:           /usr/share/locale
       qt_libraries:         /usr/lib/qt3/lib
       qt_includes:          /usr/lib/qt3/include
       KDEDIR:               /usr
       QTDIR:                /usr/lib/qt3
       Install path:         /usr/local/bin
       krusader version:     1.80.0
       krusader binary:      /usr/local/bin/krusader     (after 'make install')
       Thank you for using Krusader

       Good - your configure finished. Start make now
       bash$

   This is the output for &Mandrake;-&Linux; 10, other distributions may give a different output.

   At the end of the `./configure` script you will find a summary of the most important settings, e.g. where the &krusader; binary will be installed (after the 'make install' command). This part will also display a warning if the environment variables `KDEDIR` - `QTDIR` are empty.

   Since &krusader;-1.70.0 `./configure` has two specific &krusader; options:

   - ``./configure` `--without-konqueror`` : build &krusader; without support &konqueror;'s servicemenus, default=with. This means that &konqueror;'s right-click menu entries will not be available.

   - ``./configure` `--without-javascript`` : build &krusader; without JavaScript support, default=with. This means that the JavaScript console will not be available.

   - ``./configure` `--without-acl`` : build &krusader; without ACL support default=with. Sometimes this option is needed if you get a ACL compile error when running `make`.

   In the past the support was always compiled in when the headers where found, now you have the choice.

   Use ``./configure` `--help`` to see more options or read the `INSTALL` file in the &krusader; sources.

   If you used another --prefix= than `$KDEDIR or /usr/local`, it is recommended to do an extra check:

       $ kde-config --path exe
       /home/frank/.kde/bin/:/usr/bin/:/usr/local/bin/
       $

   If the <prefix_dir/bin> directory is not shown, you need to use e.g. `export KDEDIRS=/usr/local:/usr`. To make these settings permanent you can e.g. append this export command to your `/etc/profile` file. After that you need to restart &kde;.

   If `./configure` fails, take a look at &FAQ; missing libs or headers.

10. Start the compilation process with the `make` command.

        $ make

    This will take about 3 - 40 minutes depending on how fast your computer runs. If everything goes well, it will e.g. end with the following messages:

        foo
        make[2]: Leaving directory `/home/source/krusader_kde3/tar'
        make[2]: Entering directory `/home/source/krusader_kde3'
        make[2]: Leaving directory `/home/source/krusader_kde3'
        make[1]: Leaving directory `/home/source/krusader_kde3'
        bash$

    If `./configure` was successful and `make` failed for some reason, continue to read this page. If you can not find a solution to your problem, feel free to post a help request at our &krusader; Forum.

11. If everything is correct, you can now install &krusader;.

        $ su -c 'make install'

    You will be asked to enter your root password.

12. If you install a CVS or beta version and if &krusader; was previously installed on your computer, then you should delete the `krusaderui.rc` file in your home directory to activate the new menu entries $ ``rm` `~/.kde/share/apps/krusader/krusaderui.rc`` , click here for more info.

13. Now you can start &krusader;.

14. Optional step: Cleaning up to save disk space. Note: All compiled files created with the `make`command will be deleted.

        $ make clean

15. If you ever want to uninstall &krusader;, use

        $ su -c 'make uninstall'

    You will be asked to enter your root password.

If you followed the installation procedure and still encountered problems installing &krusader;, refer to FAQ. If the problem persists, use the help request to ask for help.

## Installing on Krusader-1.x on &MacOS;-X with KDE3.x

Since June 2006 &krusader; is added into the &krusader; finkproject.org repository Please check this url for the latest information about the &MacOS;-X port, please read the fink documentation for more information, all information below could be outdated, though they should still work :) From now on the port is maintained by Catalin Hritcu.

Krusader is ported to &MacOS; thanks the fink-project and Jonas Bähr and Bodo Tasche . Unfortunately the only *stable* kdelib-binaries which fink has to offer is currenly 3.1.4 which means you need to use &krusader;-1.40 . Unfortunately the &MacOS; X &krusader; port does not have the same power as in a native &Linux;-&kde; environment. To run &krusader; you need also X11, which doesn't interact with the rest of the &MacOS; desktop. We hope that &Qt;4/&kde;4 will solve most of these problems. If you want a more recent Krusader version you need to compile &kde;. With fink it is rather easy but it takes some CPU cycles.

Installation Instructions for &krusader;-1.40

1. Download and install fink with the &kde;3.1 binaries provided by fink and read the documentation.

2. Extract the `krusader-1.40.fink.darwin-ppc.tar.bz2` package to `/sw/fink/dist/local/main/` Only root can write here. You may have to create 'local' and 'main'.

3. Run as root: `fink install krusader`

Follow these instructions if you wish to compile more source code or use a more recent version of &krusader;:

1. Install Apple X11

2. Install the Apple X11 SDK developer-tools with X11 headers (gcc is included)

3. Install the fink-base

4. Compile kdelibs 3.4.1 or higher (fink provides the necessary `.info` files)

5. Compile the &krusader;-tarball or follow steps 2 and 3 of the previous section if a recent &krusader;-package e.g. `krusader-1.70.0.fink.darwin-ppc.tar.bz2` is available

Follow these instructions if you wish to compile &krusader;-1.80.0 :

1. Install Apple X11

2. nstall fink and enable fink unstable.

3. Compile and install the &kde; bundle in fink: fink install bundle-kde-ssl (if you get “no package found” the previous step did not succeed).

4. Use `krusader.info` (provided in the &krusader;-sourcecode) and then copy to `/sw/fink/dists/local/main/finkinfo` .

5. Compile and install &krusader; in fink: `fink install krusader`

6. Start X11 (startx) and in xterm run &krusader;

Thanks to Catalin Hritcu for these install instructions.