How to configure
----------------
To set up compilation, possibly overriding default compile-time
-options, just run
+options, just run:
./configure [<option> | -<option> | <option>=<value> ...]
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.
on other architectures you will probably need to tweak the CPU detection section
in `ucw/autoconf.cfg` and possibly also the typedefs in `ucw/config.h`.
-Then run
+Then run:
make
-which builds the whole package in the `run` directory and you can play there.
-If you want to install it anywhere else, just use
+It compiles the package. You need to install it (unless you specified
+a <<configure:local_build,local build>>). To do so, execute:
-//TODO Implement the installation
-
- make install INSTALL_DIR=/where/to/install
+ make install