|
a/src/doc/user/usermanual.sgml |
|
b/src/doc/user/usermanual.sgml |
|
... |
|
... |
| 2709 |
<title>Building from source</title>
|
2709 |
<title>Building from source</title>
|
| 2710 |
|
2710 |
|
| 2711 |
<sect2 id="rcl.install.building.prereqs">
|
2711 |
<sect2 id="rcl.install.building.prereqs">
|
| 2712 |
<title>Prerequisites</title>
|
2712 |
<title>Prerequisites</title>
|
| 2713 |
|
2713 |
|
| 2714 |
<para>At the very least, you will need to download and install the
|
2714 |
<para>C++ compiler. Up to &RCL; version 1.13.04, its absence can
|
|
|
2715 |
manifest itself by strange messages about a missing
|
|
|
2716 |
iconv_open.</para>
|
|
|
2717 |
|
|
|
2718 |
<para>Development files for
|
| 2715 |
<ulink url="http://www.xapian.org">xapian core package</ulink>
|
2719 |
<ulink url="http://www.xapian.org">
|
| 2716 |
and the <ulink
|
2720 |
<application>Xapian core</application></ulink></para>
|
|
|
2721 |
|
|
|
2722 |
<para>Development files for
|
| 2717 |
url="http://www.trolltech.com/products/qt/index.html">qt
|
2723 |
<ulink url="http://www.trolltech.com/products/qt/index.html">
|
| 2718 |
run-time and development packages</ulink>.
|
2724 |
<application>Qt</application> </ulink>.</para>
|
|
|
2725 |
|
|
|
2726 |
<para>Development files for <application>X11</application> and
|
|
|
2727 |
<application>zlib</application>.</para>
|
|
|
2728 |
|
| 2719 |
Check the <ulink url="http://www.recoll.org/download.html">
|
2729 |
<para>Check the <ulink url="http://www.recoll.org/download.html">
|
| 2720 |
&RCL; download page</ulink> for up to date version
|
2730 |
&RCL; download page</ulink> for up to date version
|
| 2721 |
information.</para>
|
2731 |
information.</para>
|
| 2722 |
|
2732 |
|
| 2723 |
<para>You will most probably be able to find a binary package for
|
2733 |
<para>You will most probably be able to find a binary package for
|
| 2724 |
<application>qt</application> for your system. You may have to
|
2734 |
<application>Qt</application> for your system. You may have to
|
| 2725 |
compile &XAP; but this is not difficult (if you are using
|
2735 |
compile &XAP; but this is not difficult (if you are using
|
| 2726 |
<application>FreeBSD</application>, there is a port).</para>
|
2736 |
<application>FreeBSD</application>, there is a port).</para>
|
| 2727 |
|
2737 |
|
| 2728 |
<para>You may also need
|
2738 |
<para>You may also need
|
| 2729 |
<ulink
|
2739 |
<ulink
|
|
... |
|
... |
| 2734 |
special.</para>
|
2744 |
special.</para>
|
| 2735 |
|
2745 |
|
| 2736 |
<sect2 id="rcl.install.building.build">
|
2746 |
<sect2 id="rcl.install.building.build">
|
| 2737 |
<title>Building</title>
|
2747 |
<title>Building</title>
|
| 2738 |
|
2748 |
|
| 2739 |
<para>&RCL; has been built on Linux, FreeBSD, macosx, and Solaris,
|
2749 |
<para>&RCL; has been built on Linux, FreeBSD, Mac OS X, and Solaris,
|
| 2740 |
most versions after 2005 should be ok, maybe some older ones too
|
2750 |
most versions after 2005 should be ok, maybe some older ones too
|
| 2741 |
(Solaris 8 is ok). If you build on another system, and
|
2751 |
(Solaris 8 is ok). If you build on another system, and
|
| 2742 |
need to modify things,
|
2752 |
need to modify things,
|
| 2743 |
<ulink url="mailto:jean-francois.dockes@wanadoo.fr">I would
|
2753 |
<ulink url="mailto:jean-francois.dockes@wanadoo.fr">I would
|
| 2744 |
very much welcome patches</ulink>.</para>
|
2754 |
very much welcome patches</ulink>.</para>
|
|
... |
|
... |
| 3449 |
<para>Here follows a small example of a personal
|
3459 |
<para>Here follows a small example of a personal
|
| 3450 |
<filename>fields</filename>
|
3460 |
<filename>fields</filename>
|
| 3451 |
file. This would extract a specific mail header and
|
3461 |
file. This would extract a specific mail header and
|
| 3452 |
use it as a searchable field, with data displayable inside result
|
3462 |
use it as a searchable field, with data displayable inside result
|
| 3453 |
lists. (Side note: as the mail filter does no decoding on the values,
|
3463 |
lists. (Side note: as the mail filter does no decoding on the values,
|
| 3454 |
only plain ascii headers can be indexed, and that only the
|
3464 |
only plain ascii headers can be indexed, and only the
|
| 3455 |
first occurrence will be used in the case of multiple occurrence
|
3465 |
first occurrence will be used for headers that occur several times).
|
| 3456 |
headers).
|
|
|
| 3457 |
|
3466 |
|
| 3458 |
<programlisting>[prefixes]
|
3467 |
<programlisting>[prefixes]
|
| 3459 |
# Index mail_mytag contents (with the given prefix)
|
3468 |
# Index mailmytag contents (with the given prefix)
|
| 3460 |
mailmytag = XMTAG
|
3469 |
mailmytag = XMTAG
|
| 3461 |
|
3470 |
|
| 3462 |
[stored]
|
3471 |
[stored]
|
| 3463 |
# Store mail_mytag inside the document data record
|
3472 |
# Store mailmytag inside the document data record (so that it can be
|
|
|
3473 |
# displayed - as %(mailmytag) - in result lists).
|
| 3464 |
mailmytag =
|
3474 |
mailmytag =
|
| 3465 |
|
3475 |
|
| 3466 |
[mail]
|
3476 |
[mail]
|
| 3467 |
# Extract the X-My-Tag mail header, and use it internally with the
|
3477 |
# Extract the X-My-Tag mail header, and use it internally with the
|
| 3468 |
# mail_mytag field name
|
3478 |
# mailmytag field name
|
| 3469 |
x-my-tag = mailmytag
|
3479 |
x-my-tag = mailmytag
|
| 3470 |
</programlisting>
|
3480 |
</programlisting>
|
| 3471 |
</para>
|
3481 |
</para>
|
| 3472 |
|
3482 |
|
| 3473 |
|
3483 |
|