Adding upstream version 1.13~rc1.upstream/1.13_rc1

Signed-off-by: Daniel Baumann <mail@daniel-baumann.ch>

1 files changed, 57 insertions, 0 deletions

diff --git a/INSTALL b/INSTALL
new file mode 100644
index 0000000..c2a3dcc
--- /dev/null
+++ b/INSTALL
@@ -0,0 +1,57 @@
+Requirements
+------------
+You will need a C++ compiler.
+I use gcc 4.3.5 and 3.3.6, but the code should compile with any
+standards compliant compiler.
+Gcc is available at http://gcc.gnu.org.
+
+
+Procedure
+---------
+1. Unpack the archive if you have not done so already:
+
+	lzip -cd lziprecover[version].tar.lz | tar -xf -
+or
+	gzip -cd lziprecover[version].tar.gz | tar -xf -
+
+This creates the directory ./lziprecover[version] containing the source
+from the main archive.
+
+2. Change to lziprecover directory and run configure.
+   (Try `configure --help' for usage instructions).
+
+	cd lziprecover[version]
+	./configure
+
+3. Run make.
+
+	make
+
+4. Optionally, type `make check' to run the tests that come with
+   lziprecover.
+
+5. Type `make install' to install the programs and any data files and
+   documentation.
+
+
+Another way
+-----------
+You can also compile lziprecover into a separate directory. To do this,
+you must use a version of `make' that supports the `VPATH' variable,
+such as GNU `make'. `cd' to the directory where you want the object
+files and executables to go and run the `configure' script. `configure'
+automatically checks for the source code in `.', in `..' and in the
+directory that `configure' is in.
+
+`configure' recognizes the option `--srcdir=DIR' to control where to
+look for the sources. Usually `configure' can determine that directory
+automatically.
+
+After running `configure', you can run `make' and `make install' as
+explained above.
+
+
+Copyright (C) 2009, 2010, 2011 Antonio Diaz Diaz.
+
+This file is free documentation: you have unlimited permission to copy,
+distribute and modify it.