Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

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