--- a/src/INSTALL
+++ b/src/INSTALL
@@ -178,8 +178,8 @@
ok). If you build on another system, and need to modify things, I would
very much welcome patches.
- Depending on the qt configuration on your system, you may have to set the
- QTDIR and QMAKESPECS variables in your environment:
+ Depending on the Qt 3 configuration on your system, you may have to set
+ the QTDIR and QMAKESPECS variables in your environment:
* QTDIR should point to the directory above the one that holds the qt
include files (ie: if qt.h is /usr/local/qt/include/qt.h, QTDIR should
@@ -189,8 +189,11 @@
sub-directories (ie: linux-g++).
On many Linux systems, QTDIR is set by the login scripts, and QMAKESPECS
- is not needed because there is a default link in mkspecs/. Neither should
- be needed with Qt 4.
+ is not needed because there is a default link in mkspecs/.
+
+ Neither QTDIR nor QMAKESPECS should be needed with Qt 4, configuration
+ details are entirely determined by qmake (which is quite often installed
+ as qmake-qt4).
Configure options:
@@ -219,6 +222,8 @@
* --without-gui Disable the Qt interface, and auxiliary uses of X11, and
compile the command line version.
+ * Of course the usual autoconf configure options, like --prefix apply.
+
Normal procedure:
cd recoll-xxx
@@ -239,10 +244,12 @@
the source tree. This will copy the commands to prefix/bin and the sample
configuration files, scripts and other shared data to prefix/share/recoll.
- If the installation prefix given to recollinstall is different from what
- was specified when executing configure, you will have to set the
+ If the installation prefix given to recollinstall is different from either
+ the system default or the value which was specified when executing
+ configure (as in configure --prefix /some/path), you will have to set the
RECOLL_DATADIR environment variable to indicate where the shared data is
- to be found.
+ to be found (ie for (ba)sh: export
+ RECOLL_DATADIR=/some/path/share/recoll).
You can then proceed to configuration.
@@ -318,12 +325,13 @@
* Section definition ([somedirname]).
- Section definitions allow redefining some parameters for a directory
- sub-tree. They stay in effect until another section definition, or the end
- of file, is encountered. Some of the parameters used for indexing are
- looked up hierarchically from the current directory location upwards. Not
- all parameters can be meaningfully redefined, this is specified for each
- in the next section.
+ Depending on the type of configuration file, section definitions either
+ separate groups of parameters or allow redefining some parameters for a
+ directory sub-tree. They stay in effect until another section definition,
+ or the end of file, is encountered. Some of the parameters used for
+ indexing are looked up hierarchically from the current directory location
+ upwards. Not all parameters can be meaningfully redefined, this is
+ specified for each in the next section.
When found at the beginning of a file path, the tilde character (~) is
expanded to the name of the user's home directory, as a shell would do.