X-Git-Url: http://mj.ucw.cz/gitweb/?a=blobdiff_plain;f=ucw%2Fdoc%2Fconfigure.txt;h=35784a25177a936fe202b86159f707c33d698b69;hb=947469a68a50754eafe654f9f256411c07b2ca6a;hp=5dd3c7ac048ec295a49dd80c76660c929b9e0017;hpb=d353c2a2c76a432f089adff3d937167d10e67611;p=libucw.git

diff --git a/ucw/doc/configure.txt b/ucw/doc/configure.txt
index 5dd3c7ac..35784a25 100644
--- a/ucw/doc/configure.txt
+++ b/ucw/doc/configure.txt
@@ -1,44 +1,15 @@
-How to Configure Sherlock
-=========================
+How to Configure Sherlock libraries
+===================================
 
 What can be configured
 ----------------------
 There are two different levels of configuring/customizing program
-based on libucw:
+based on sherlock libraries:
 
-  - runtime configuration in configuration files (see doc/config)
-
-  - compile-time configuration: config switches set before compiling, selecting
-    optional features.
-
-  - customization: a set of C declarations and functions, which define word
-    types, attributes and the ways to match them. In most cases, you should
-    use the "free" customization designed for searching in web pages and similar
-    documents. If you want just a simple search engine for indexing databases,
-    the "customs/bare" customization can be better. If you want to extend Sherlock
-    beyond that, you will probably need to write your own customization -- just
-    follow the structure of the "free" customization and the comments there.
-
-
-How to configure
-----------------
-To set up compilation for a given customization, possibly overriding its default
-compile-time options, just run
-
-	./configure <customization> [<option> | -<option> | <option>=<value> ...]
-
-The default values of feature options are taken from sherlock/default.cfg and modified
-by <customization>/config. Compiler flags and options dependent on compiler, OS and
-CPU type are set in ucw/autoconf.cfg. Everything can be overriden by options specified
-on the configure's command line, which have the highest priority.
-
-If you want to see the resulting set of options, take a look at obj/config.mk.
-
-Options specifying compiler/linker/debugger options can be also overriden during
-compilation by `make <option>=<value>`. While it's also possible to specify the other
-options in this way, it probably won't have the desired effect, because configure
-also generates C include files containing the options.
+  - runtime configuration in configuration files (see <<config:>>)
 
+  - compile-time configuration of the libraries: config switches set
+    before compiling, selecting optional features.
 
 Where to build
 --------------
@@ -52,3 +23,52 @@ want to build several different configurations from a single source tree). In or
 to do that, switch to the destination directory and issue `<source-dir>/configure ...`.
 This way, configure will create the `obj` and `run` directories locally and set up
 a Makefile which refers to the original source tree.
+
+How to configure
+----------------
+To set up compilation, possibly overriding default compile-time
+options, just run:
+
+	./configure [<option> | -<option> | <option>=<value> ...]
+
+The default values of feature options are taken from `default.cfg`.
+Compiler flags and options dependent on compiler, OS and CPU type
+are set in `ucw/perl/UCW/Configure/C.pm`. Everything can be overriden by
+options specified on the configure's command line, which have the highest
+priority.
+
+If you want to see the resulting set of options, take a look at
+`obj/config.mk`.
+
+Options specifying compiler/linker/debugger options can be also overriden
+during compilation by `make <option>=<value>`. While it's also possible
+to specify the other options in this way, it probably won't have the desired
+effect, because configure also generates C include files containing the
+options.
+
+Installation options
+--------------------
+By default, the package is compiled to be installed and it chooses a
+place where it will install. If you want to place it somewhere else,
+set the `PREFIX` option:
+
+	./configure PREFIX=/where/to/install
+
+[[local_build]]
+You can create a local compilation, which does not need to be
+installed. All paths are set relative to a `run` directory and
+programs expect to have current working directory set to it. However,
+you can move the `run` directory around your filesystem as you like.
+To compile it that way, turn on the `CONFIG_LOCAL` option (and do not
+set `PREFIX`):
+
+	./configure CONFIG_LOCAL
+
+Examples
+--------
+  - `./configure -CONFIG_SHARED` will build the libraries statically.
+  - `./configure -CONFIG_IMAGES` avoids building the image library.
+  - `./configure CONFIG_UCW_ONLY -CONFIG_UCW_UTILS` compiles only the
+    libucw library without its util programs.
+  - `./configure CONFIG_XML PREFIX=$HOME/sherlock` includes a xml
+    library and installs into your home directory.