1-*- Text -*-
2
3XDelta depends on
4
5	glib 1.2.8 or later
6	zlib 1.1.3 or later
7
8You can get glib from
9
10	ftp://ftp.gtk.org/pub/gtk/v1.2
11
12You can get zlib from
13
14	ftp://ftp.cdrom.com/pub/infozip/zlib
15
16To install, make sure these packages are installed and your compiler
17and linker either locates zlib by default or that the CFLAGS
18environment variable contains an appropriate include directive and the
19LDFLAGS environment variable contains a suitable linker directive.
20
21Then run
22
23	./configure
24
25Then run
26
27	make
28
29Then run
30
31	make install
32
33Below follows the standard GNU INSTALL file, which contains general
34troubleshooting tips.
35
36Basic Installation
37==================
38
39   These are generic installation instructions.
40
41   The `configure' shell script attempts to guess correct values for
42various system-dependent variables used during compilation.  It uses
43those values to create a `Makefile' in each directory of the package.
44It may also create one or more `.h' files containing system-dependent
45definitions.  Finally, it creates a shell script `config.status' that
46you can run in the future to recreate the current configuration, a file
47`config.cache' that saves the results of its tests to speed up
48reconfiguring, and a file `config.log' containing compiler output
49(useful mainly for debugging `configure').
50
51   If you need to do unusual things to compile the package, please try
52to figure out how `configure' could check whether to do them, and mail
53diffs or instructions to the address given in the `README' so they can
54be considered for the next release.  If at some point `config.cache'
55contains results you don't want to keep, you may remove or edit it.
56
57   The file `configure.in' is used to create `configure' by a program
58called `autoconf'.  You only need `configure.in' if you want to change
59it or regenerate `configure' using a newer version of `autoconf'.
60
61The simplest way to compile this package is:
62
63  1. `cd' to the directory containing the package's source code and type
64     `./configure' to configure the package for your system.  If you're
65     using `csh' on an old version of System V, you might need to type
66     `sh ./configure' instead to prevent `csh' from trying to execute
67     `configure' itself.
68
69     Running `configure' takes awhile.  While running, it prints some
70     messages telling which features it is checking for.
71
72  2. Type `make' to compile the package.
73
74  3. Optionally, type `make check' to run any self-tests that come with
75     the package.
76
77  4. Type `make install' to install the programs and any data files and
78     documentation.
79
80  5. You can remove the program binaries and object files from the
81     source code directory by typing `make clean'.  To also remove the
82     files that `configure' created (so you can compile the package for
83     a different kind of computer), type `make distclean'.  There is
84     also a `make maintainer-clean' target, but that is intended mainly
85     for the package's developers.  If you use it, you may have to get
86     all sorts of other programs in order to regenerate files that came
87     with the distribution.
88
89Compilers and Options
90=====================
91
92   Some systems require unusual options for compilation or linking that
93the `configure' script does not know about.  You can give `configure'
94initial values for variables by setting them in the environment.  Using
95a Bourne-compatible shell, you can do that on the command line like
96this:
97     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
98
99Or on systems that have the `env' program, you can do it like this:
100     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
101
102Compiling For Multiple Architectures
103====================================
104
105   You can compile the package for more than one kind of computer at the
106same time, by placing the object files for each architecture in their
107own directory.  To do this, you must use a version of `make' that
108supports the `VPATH' variable, such as GNU `make'.  `cd' to the
109directory where you want the object files and executables to go and run
110the `configure' script.  `configure' automatically checks for the
111source code in the directory that `configure' is in and in `..'.
112
113   If you have to use a `make' that does not supports the `VPATH'
114variable, you have to compile the package for one architecture at a time
115in the source code directory.  After you have installed the package for
116one architecture, use `make distclean' before reconfiguring for another
117architecture.
118
119Installation Names
120==================
121
122   By default, `make install' will install the package's files in
123`/usr/local/bin', `/usr/local/man', etc.  You can specify an
124installation prefix other than `/usr/local' by giving `configure' the
125option `--prefix=PATH'.
126
127   You can specify separate installation prefixes for
128architecture-specific files and architecture-independent files.  If you
129give `configure' the option `--exec-prefix=PATH', the package will use
130PATH as the prefix for installing programs and libraries.
131Documentation and other data files will still use the regular prefix.
132
133   In addition, if you use an unusual directory layout you can give
134options like `--bindir=PATH' to specify different values for particular
135kinds of files.  Run `configure --help' for a list of the directories
136you can set and what kinds of files go in them.
137
138   If the package supports it, you can cause programs to be installed
139with an extra prefix or suffix on their names by giving `configure' the
140option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
141
142Optional Features
143=================
144
145   Some packages pay attention to `--enable-FEATURE' options to
146`configure', where FEATURE indicates an optional part of the package.
147They may also pay attention to `--with-PACKAGE' options, where PACKAGE
148is something like `gnu-as' or `x' (for the X Window System).  The
149`README' should mention any `--enable-' and `--with-' options that the
150package recognizes.
151
152   For packages that use the X Window System, `configure' can usually
153find the X include and library files automatically, but if it doesn't,
154you can use the `configure' options `--x-includes=DIR' and
155`--x-libraries=DIR' to specify their locations.
156
157Specifying the System Type
158==========================
159
160   There may be some features `configure' can not figure out
161automatically, but needs to determine by the type of host the package
162will run on.  Usually `configure' can figure that out, but if it prints
163a message saying it can not guess the host type, give it the
164`--host=TYPE' option.  TYPE can either be a short name for the system
165type, such as `sun4', or a canonical name with three fields:
166     CPU-COMPANY-SYSTEM
167
168See the file `config.sub' for the possible values of each field.  If
169`config.sub' isn't included in this package, then this package doesn't
170need to know the host type.
171
172   If you are building compiler tools for cross-compiling, you can also
173use the `--target=TYPE' option to select the type of system they will
174produce code for and the `--build=TYPE' option to select the type of
175system on which you are compiling the package.
176
177Sharing Defaults
178================
179
180   If you want to set default values for `configure' scripts to share,
181you can create a site shell script called `config.site' that gives
182default values for variables like `CC', `cache_file', and `prefix'.
183`configure' looks for `PREFIX/share/config.site' if it exists, then
184`PREFIX/etc/config.site' if it exists.  Or, you can set the
185`CONFIG_SITE' environment variable to the location of the site script.
186A warning: not all `configure' scripts look for a site script.
187
188Operation Controls
189==================
190
191   `configure' recognizes the following options to control how it
192operates.
193
194`--cache-file=FILE'
195     Use and save the results of the tests in FILE instead of
196     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
197     debugging `configure'.
198
199`--help'
200     Print a summary of the options to `configure', and exit.
201
202`--quiet'
203`--silent'
204`-q'
205     Do not print messages saying which checks are being made.  To
206     suppress all normal output, redirect it to `/dev/null' (any error
207     messages will still be shown).
208
209`--srcdir=DIR'
210     Look for the package's source code in directory DIR.  Usually
211     `configure' can determine that directory automatically.
212
213`--version'
214     Print the version of Autoconf used to generate the `configure'
215     script, and exit.
216
217`configure' also accepts some other, not widely useful, options.
218