Chapter 7. Installation

Table of Contents
7.1. Installing a binary copy
7.2. Supporting packages
7.3. Building from source
7.4. Configuration overview
7.5. The KDE Kicker Recoll applet

7.1. Installing a binary copy

There are three types of binary Recoll installations:

In all cases, the strict software dependancies (ie on Xapian or iconv) will be automatically satisfied, you should not have to worry about them.

You will only have to check or install supporting applications for the file types that you want to index beyond those that are natively processed by Recoll (text, HTML, mail files, and a few others).

You should also maybe have a look at the configuration section (but this may not be necessary for a quick test with default parameters). Most parameters can be more conveniently set from the GUI interface.

7.1.1. Installing through a package system

If you use a BSD-type port system or a prebuilt package (DEB, RPM, manually or through the system software configuration utility), just follow the usual procedure for your system.

7.1.2. Installing a prebuilt Recoll

The unpackaged binary versions on the Recoll web site are just compressed tar files of a build tree, where only the useful parts were kept (executables and sample configuration).

The executable binary files are built with a static link to libxapian and libiconv, to make installation easier (no dependencies).

After extracting the tar file, you can proceed with installation as if you had built the package from source (that is, just type make install). The binary trees are built for installation to /usr/local.