source: trunk/INSTALL @ 96

Last change on this file since 96 was 96, checked in by Jari Häkkinen, 15 years ago

Added --with-apr and --with-svn options to configure script. These may be needed for compilation success.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Id
File size: 10.4 KB
Line 
1$Id: INSTALL 96 2006-03-28 23:00:51Z jari $
2
3Copyright (C) 2006 Jari Häkkinen
4
5Files are copyright by their respective authors. The contributions to
6files where copyright is not explicitly stated can be traced with the
7source code revision system.
8
9This file is part of svnstat, http://lev.thep.lu.se/trac/svnstat
10
11svnstat is free software; you can redistribute it and/or modify it
12under the terms of the GNU General Public License as published by the
13Free Software Foundation; either version 2 of the License, or (at your
14option) any later version.
15
16svnstat is distributed in the hope that it will be useful, but WITHOUT
17ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
18FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
19for more details.
20
21You should have received a copy of the GNU General Public License
22along with this program; if not, write to the Free Software
23Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307,
24USA.
25
26
27
28Below you'll find the generic FSF install instructions. To compile
29and install svnstat you can follow the usual autoconf path:
30
31# ./configure
32# make
33# make install
34
35With an optional
36
37# make check
38
39The 'configure' script accepts two options of interest for
40svnstat. You can provide 'configure' with APR and subversion API
41location information with --with-apr=DIR and --with-svn=DIR,
42respectively.
43
44
45
46FSF generic install documentation:
47
48Installation Instructions
49*************************
50
51Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004 Free
52Software Foundation, Inc.
53
54This file is free documentation; the Free Software Foundation gives
55unlimited permission to copy, distribute and modify it.
56
57Basic Installation
58==================
59
60These are generic installation instructions.
61
62   The `configure' shell script attempts to guess correct values for
63various system-dependent variables used during compilation.  It uses
64those values to create a `Makefile' in each directory of the package.
65It may also create one or more `.h' files containing system-dependent
66definitions.  Finally, it creates a shell script `config.status' that
67you can run in the future to recreate the current configuration, and a
68file `config.log' containing compiler output (useful mainly for
69debugging `configure').
70
71   It can also use an optional file (typically called `config.cache'
72and enabled with `--cache-file=config.cache' or simply `-C') that saves
73the results of its tests to speed up reconfiguring.  (Caching is
74disabled by default to prevent problems with accidental use of stale
75cache files.)
76
77   If you need to do unusual things to compile the package, please try
78to figure out how `configure' could check whether to do them, and mail
79diffs or instructions to the address given in the `README' so they can
80be considered for the next release.  If you are using the cache, and at
81some point `config.cache' contains results you don't want to keep, you
82may remove or edit it.
83
84   The file `configure.ac' (or `configure.in') is used to create
85`configure' by a program called `autoconf'.  You only need
86`configure.ac' if you want to change it or regenerate `configure' using
87a newer version of `autoconf'.
88
89The simplest way to compile this package is:
90
91  1. `cd' to the directory containing the package's source code and type
92     `./configure' to configure the package for your system.  If you're
93     using `csh' on an old version of System V, you might need to type
94     `sh ./configure' instead to prevent `csh' from trying to execute
95     `configure' itself.
96
97     Running `configure' takes awhile.  While running, it prints some
98     messages telling which features it is checking for.
99
100  2. Type `make' to compile the package.
101
102  3. Optionally, type `make check' to run any self-tests that come with
103     the package.
104
105  4. Type `make install' to install the programs and any data files and
106     documentation.
107
108  5. You can remove the program binaries and object files from the
109     source code directory by typing `make clean'.  To also remove the
110     files that `configure' created (so you can compile the package for
111     a different kind of computer), type `make distclean'.  There is
112     also a `make maintainer-clean' target, but that is intended mainly
113     for the package's developers.  If you use it, you may have to get
114     all sorts of other programs in order to regenerate files that came
115     with the distribution.
116
117Compilers and Options
118=====================
119
120Some systems require unusual options for compilation or linking that the
121`configure' script does not know about.  Run `./configure --help' for
122details on some of the pertinent environment variables.
123
124   You can give `configure' initial values for configuration parameters
125by setting variables in the command line or in the environment.  Here
126is an example:
127
128     ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
129
130   *Note Defining Variables::, for more details.
131
132Compiling For Multiple Architectures
133====================================
134
135You can compile the package for more than one kind of computer at the
136same time, by placing the object files for each architecture in their
137own directory.  To do this, you must use a version of `make' that
138supports the `VPATH' variable, such as GNU `make'.  `cd' to the
139directory where you want the object files and executables to go and run
140the `configure' script.  `configure' automatically checks for the
141source code in the directory that `configure' is in and in `..'.
142
143   If you have to use a `make' that does not support the `VPATH'
144variable, you have to compile the package for one architecture at a
145time in the source code directory.  After you have installed the
146package for one architecture, use `make distclean' before reconfiguring
147for another architecture.
148
149Installation Names
150==================
151
152By default, `make install' will install the package's files in
153`/usr/local/bin', `/usr/local/man', etc.  You can specify an
154installation prefix other than `/usr/local' by giving `configure' the
155option `--prefix=PREFIX'.
156
157   You can specify separate installation prefixes for
158architecture-specific files and architecture-independent files.  If you
159give `configure' the option `--exec-prefix=PREFIX', the package will
160use PREFIX as the prefix for installing programs and libraries.
161Documentation and other data files will still use the regular prefix.
162
163   In addition, if you use an unusual directory layout you can give
164options like `--bindir=DIR' to specify different values for particular
165kinds of files.  Run `configure --help' for a list of the directories
166you can set and what kinds of files go in them.
167
168   If the package supports it, you can cause programs to be installed
169with an extra prefix or suffix on their names by giving `configure' the
170option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
171
172Optional Features
173=================
174
175Some packages pay attention to `--enable-FEATURE' options to
176`configure', where FEATURE indicates an optional part of the package.
177They may also pay attention to `--with-PACKAGE' options, where PACKAGE
178is something like `gnu-as' or `x' (for the X Window System).  The
179`README' should mention any `--enable-' and `--with-' options that the
180package recognizes.
181
182   For packages that use the X Window System, `configure' can usually
183find the X include and library files automatically, but if it doesn't,
184you can use the `configure' options `--x-includes=DIR' and
185`--x-libraries=DIR' to specify their locations.
186
187Specifying the System Type
188==========================
189
190There may be some features `configure' cannot figure out automatically,
191but needs to determine by the type of machine the package will run on.
192Usually, assuming the package is built to be run on the _same_
193architectures, `configure' can figure that out, but if it prints a
194message saying it cannot guess the machine type, give it the
195`--build=TYPE' option.  TYPE can either be a short name for the system
196type, such as `sun4', or a canonical name which has the form:
197
198     CPU-COMPANY-SYSTEM
199
200where SYSTEM can have one of these forms:
201
202     OS KERNEL-OS
203
204   See the file `config.sub' for the possible values of each field.  If
205`config.sub' isn't included in this package, then this package doesn't
206need to know the machine type.
207
208   If you are _building_ compiler tools for cross-compiling, you should
209use the `--target=TYPE' option to select the type of system they will
210produce code for.
211
212   If you want to _use_ a cross compiler, that generates code for a
213platform different from the build platform, you should specify the
214"host" platform (i.e., that on which the generated programs will
215eventually be run) with `--host=TYPE'.
216
217Sharing Defaults
218================
219
220If you want to set default values for `configure' scripts to share, you
221can create a site shell script called `config.site' that gives default
222values for variables like `CC', `cache_file', and `prefix'.
223`configure' looks for `PREFIX/share/config.site' if it exists, then
224`PREFIX/etc/config.site' if it exists.  Or, you can set the
225`CONFIG_SITE' environment variable to the location of the site script.
226A warning: not all `configure' scripts look for a site script.
227
228Defining Variables
229==================
230
231Variables not defined in a site shell script can be set in the
232environment passed to `configure'.  However, some packages may run
233configure again during the build, and the customized values of these
234variables may be lost.  In order to avoid this problem, you should set
235them in the `configure' command line, using `VAR=value'.  For example:
236
237     ./configure CC=/usr/local2/bin/gcc
238
239will cause the specified gcc to be used as the C compiler (unless it is
240overridden in the site shell script).
241
242`configure' Invocation
243======================
244
245`configure' recognizes the following options to control how it operates.
246
247`--help'
248`-h'
249     Print a summary of the options to `configure', and exit.
250
251`--version'
252`-V'
253     Print the version of Autoconf used to generate the `configure'
254     script, and exit.
255
256`--cache-file=FILE'
257     Enable the cache: use and save the results of the tests in FILE,
258     traditionally `config.cache'.  FILE defaults to `/dev/null' to
259     disable caching.
260
261`--config-cache'
262`-C'
263     Alias for `--cache-file=config.cache'.
264
265`--quiet'
266`--silent'
267`-q'
268     Do not print messages saying which checks are being made.  To
269     suppress all normal output, redirect it to `/dev/null' (any error
270     messages will still be shown).
271
272`--srcdir=DIR'
273     Look for the package's source code in directory DIR.  Usually
274     `configure' can determine that directory automatically.
275
276`configure' also accepts some other, not widely useful, options.  Run
277`configure --help' for more details.
278
Note: See TracBrowser for help on using the repository browser.