This release is frozen and still contains bugs which have been corrected in later releases. Only "compatibility" bugs will be accepted.
lxr.conf
which MUST be located in the LXR root directory.
templates/
subdirectory.
But a tailored copy has been stored in the
lxrconf.d/
directory
by the pre-configuration step.
lxrconf.d/lxr.conf
with your favorite editor
(vi, emacs, KWrite,
gedit, …).
If the pre-configuration step reported both glimpse and swish-e were found on your computer, you must comment out one of the following directive groups:
or:
'glimpsebin'
or 'swishbin'
by prefixing the line with a pound sign (#
).
The host name (complete with protocol and port) comes from
parameter 'host_names'
,
a list of the different names under which your host is
known to your web server and the DNS servers.
http:
.
According to your choice of a search engine,
have the 'htmlsearch'
point to the
right template;
choose one of the following:
The access URL is the concatenation of the host name and the virtual root to the script.
Parameter 'virtroot'
is equal to what
comes after the hostname to complete the access URL.
Give a nice title to be displayed on every page:
Set parameter 'sourceroot'
to the
absolute path of the directory containing the different
versions (as subdirectories):
Give a name for the root of relative paths within your tree:
or, to have version identifier inserted:
Insert into parameter 'range'
the names of the subdirectories containing
the versions:
And modify 'default'
to preselect
which version LXR will display at start-time.
If your source files use include
directives,
set 'incprefix'
to the list of
include directories.
Tell which data base to use in
'dbname'
among the following three:
lxr
is the name given
when creating the database (see the previous step).
Do not forget to adjust the access parameters as you defined them in the previous step:
'dbprefix'
only if it is different from the default.
And last, give the search engine some room for its private usage:
lxr.conf
to its final location:
For an example of parameter values for the demo trees on SourceForge, see here.
You're now ready to load the database with your data.