Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Newer
Older
100644 302 lines (225 sloc) 11.696 kb
e1ae3e6 @xsisqox Revert "Remove Wallpaper support"
authored
1 For basic instruction how to install software from source, please read
2 "Installation Instructions" below!
3
4 Optional features:
5
6 * Setting image as wallpaper
e303842 @xsisqox Viewnior 1.3 released!
authored
7 This feature is working on GNOME, XFCE, LXDE and FluxBox without additional
8 configuration parameters and package dependecies.
6fd4200 @xsisqox Viewnior 0.6 released!
authored
9
e1ae3e6 @xsisqox Revert "Remove Wallpaper support"
authored
10
62a80c1 @xsisqox Major changes made, so that source code is
authored
11 Installation Instructions
12 *************************
13
14 Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
530e891 @xsisqox Update INSTALL
authored
15 2006, 2007, 2008 Free Software Foundation, Inc.
62a80c1 @xsisqox Major changes made, so that source code is
authored
16
530e891 @xsisqox Update INSTALL
authored
17 This file is free documentation; the Free Software Foundation gives
62a80c1 @xsisqox Major changes made, so that source code is
authored
18 unlimited permission to copy, distribute and modify it.
19
20 Basic Installation
21 ==================
22
530e891 @xsisqox Update INSTALL
authored
23 Briefly, the shell commands `./configure; make; make install' should
62a80c1 @xsisqox Major changes made, so that source code is
authored
24 configure, build, and install this package. The following
25 more-detailed instructions are generic; see the `README' file for
26 instructions specific to this package.
27
28 The `configure' shell script attempts to guess correct values for
29 various system-dependent variables used during compilation. It uses
30 those values to create a `Makefile' in each directory of the package.
31 It may also create one or more `.h' files containing system-dependent
32 definitions. Finally, it creates a shell script `config.status' that
33 you can run in the future to recreate the current configuration, and a
34 file `config.log' containing compiler output (useful mainly for
35 debugging `configure').
36
37 It can also use an optional file (typically called `config.cache'
38 and enabled with `--cache-file=config.cache' or simply `-C') that saves
39 the results of its tests to speed up reconfiguring. Caching is
40 disabled by default to prevent problems with accidental use of stale
41 cache files.
42
43 If you need to do unusual things to compile the package, please try
44 to figure out how `configure' could check whether to do them, and mail
45 diffs or instructions to the address given in the `README' so they can
46 be considered for the next release. If you are using the cache, and at
47 some point `config.cache' contains results you don't want to keep, you
48 may remove or edit it.
49
50 The file `configure.ac' (or `configure.in') is used to create
51 `configure' by a program called `autoconf'. You need `configure.ac' if
52 you want to change it or regenerate `configure' using a newer version
53 of `autoconf'.
54
55 The simplest way to compile this package is:
56
57 1. `cd' to the directory containing the package's source code and type
58 `./configure' to configure the package for your system.
59
60 Running `configure' might take a while. While running, it prints
61 some messages telling which features it is checking for.
62
63 2. Type `make' to compile the package.
64
65 3. Optionally, type `make check' to run any self-tests that come with
66 the package.
67
68 4. Type `make install' to install the programs and any data files and
69 documentation.
70
71 5. You can remove the program binaries and object files from the
72 source code directory by typing `make clean'. To also remove the
73 files that `configure' created (so you can compile the package for
74 a different kind of computer), type `make distclean'. There is
75 also a `make maintainer-clean' target, but that is intended mainly
76 for the package's developers. If you use it, you may have to get
77 all sorts of other programs in order to regenerate files that came
78 with the distribution.
79
80 6. Often, you can also type `make uninstall' to remove the installed
81 files again.
82
83 Compilers and Options
84 =====================
85
530e891 @xsisqox Update INSTALL
authored
86 Some systems require unusual options for compilation or linking that
87 the `configure' script does not know about. Run `./configure --help'
88 for details on some of the pertinent environment variables.
62a80c1 @xsisqox Major changes made, so that source code is
authored
89
90 You can give `configure' initial values for configuration parameters
91 by setting variables in the command line or in the environment. Here
92 is an example:
93
94 ./configure CC=c99 CFLAGS=-g LIBS=-lposix
95
96 *Note Defining Variables::, for more details.
97
98 Compiling For Multiple Architectures
99 ====================================
100
530e891 @xsisqox Update INSTALL
authored
101 You can compile the package for more than one kind of computer at the
62a80c1 @xsisqox Major changes made, so that source code is
authored
102 same time, by placing the object files for each architecture in their
103 own directory. To do this, you can use GNU `make'. `cd' to the
104 directory where you want the object files and executables to go and run
105 the `configure' script. `configure' automatically checks for the
106 source code in the directory that `configure' is in and in `..'.
107
108 With a non-GNU `make', it is safer to compile the package for one
109 architecture at a time in the source code directory. After you have
110 installed the package for one architecture, use `make distclean' before
111 reconfiguring for another architecture.
112
530e891 @xsisqox Update INSTALL
authored
113 On MacOS X 10.5 and later systems, you can create libraries and
114 executables that work on multiple system types--known as "fat" or
115 "universal" binaries--by specifying multiple `-arch' options to the
116 compiler but only a single `-arch' option to the preprocessor. Like
117 this:
118
119 ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
120 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
121 CPP="gcc -E" CXXCPP="g++ -E"
122
123 This is not guaranteed to produce working output in all cases, you
124 may have to build one architecture at a time and combine the results
125 using the `lipo' tool if you have problems.
126
62a80c1 @xsisqox Major changes made, so that source code is
authored
127 Installation Names
128 ==================
129
530e891 @xsisqox Update INSTALL
authored
130 By default, `make install' installs the package's commands under
62a80c1 @xsisqox Major changes made, so that source code is
authored
131 `/usr/local/bin', include files under `/usr/local/include', etc. You
132 can specify an installation prefix other than `/usr/local' by giving
133 `configure' the option `--prefix=PREFIX'.
134
135 You can specify separate installation prefixes for
136 architecture-specific files and architecture-independent files. If you
137 pass the option `--exec-prefix=PREFIX' to `configure', the package uses
138 PREFIX as the prefix for installing programs and libraries.
139 Documentation and other data files still use the regular prefix.
140
141 In addition, if you use an unusual directory layout you can give
142 options like `--bindir=DIR' to specify different values for particular
143 kinds of files. Run `configure --help' for a list of the directories
144 you can set and what kinds of files go in them.
145
146 If the package supports it, you can cause programs to be installed
147 with an extra prefix or suffix on their names by giving `configure' the
148 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
149
150 Optional Features
151 =================
152
530e891 @xsisqox Update INSTALL
authored
153 Some packages pay attention to `--enable-FEATURE' options to
62a80c1 @xsisqox Major changes made, so that source code is
authored
154 `configure', where FEATURE indicates an optional part of the package.
155 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
156 is something like `gnu-as' or `x' (for the X Window System). The
157 `README' should mention any `--enable-' and `--with-' options that the
158 package recognizes.
159
160 For packages that use the X Window System, `configure' can usually
161 find the X include and library files automatically, but if it doesn't,
162 you can use the `configure' options `--x-includes=DIR' and
163 `--x-libraries=DIR' to specify their locations.
164
530e891 @xsisqox Update INSTALL
authored
165 Particular systems
166 ==================
167
168 On HP-UX, the default C compiler is not ANSI C compatible. If GNU
169 CC is not installed, it is recommended to use the following options in
170 order to use an ANSI C compiler:
171
172 ./configure CC="cc -Ae"
173
174 and if that doesn't work, install pre-built binaries of GCC for HP-UX.
175
176 On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
177 parse its `<wchar.h>' header file. The option `-nodtk' can be used as
178 a workaround. If GNU CC is not installed, it is therefore recommended
179 to try
180
181 ./configure CC="cc"
182
183 and if that doesn't work, try
184
185 ./configure CC="cc -nodtk"
186
62a80c1 @xsisqox Major changes made, so that source code is
authored
187 Specifying the System Type
188 ==========================
189
530e891 @xsisqox Update INSTALL
authored
190 There may be some features `configure' cannot figure out
191 automatically, but needs to determine by the type of machine the package
192 will run on. Usually, assuming the package is built to be run on the
193 _same_ architectures, `configure' can figure that out, but if it prints
194 a message saying it cannot guess the machine type, give it the
62a80c1 @xsisqox Major changes made, so that source code is
authored
195 `--build=TYPE' option. TYPE can either be a short name for the system
196 type, such as `sun4', or a canonical name which has the form:
197
198 CPU-COMPANY-SYSTEM
199
200 where 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
206 need to know the machine type.
207
208 If you are _building_ compiler tools for cross-compiling, you should
209 use the option `--target=TYPE' to select the type of system they will
210 produce code for.
211
212 If you want to _use_ a cross compiler, that generates code for a
213 platform different from the build platform, you should specify the
214 "host" platform (i.e., that on which the generated programs will
215 eventually be run) with `--host=TYPE'.
216
217 Sharing Defaults
218 ================
219
530e891 @xsisqox Update INSTALL
authored
220 If you want to set default values for `configure' scripts to share,
221 you can create a site shell script called `config.site' that gives
222 default values for variables like `CC', `cache_file', and `prefix'.
62a80c1 @xsisqox Major changes made, so that source code is
authored
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.
226 A warning: not all `configure' scripts look for a site script.
227
228 Defining Variables
229 ==================
230
530e891 @xsisqox Update INSTALL
authored
231 Variables not defined in a site shell script can be set in the
62a80c1 @xsisqox Major changes made, so that source code is
authored
232 environment passed to `configure'. However, some packages may run
233 configure again during the build, and the customized values of these
234 variables may be lost. In order to avoid this problem, you should set
235 them in the `configure' command line, using `VAR=value'. For example:
236
237 ./configure CC=/usr/local2/bin/gcc
238
239 causes the specified `gcc' to be used as the C compiler (unless it is
240 overridden in the site shell script).
241
242 Unfortunately, this technique does not work for `CONFIG_SHELL' due to
243 an Autoconf bug. Until the bug is fixed you can use this workaround:
244
245 CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
246
247 `configure' Invocation
248 ======================
249
530e891 @xsisqox Update INSTALL
authored
250 `configure' recognizes the following options to control how it
251 operates.
62a80c1 @xsisqox Major changes made, so that source code is
authored
252
253 `--help'
254 `-h'
530e891 @xsisqox Update INSTALL
authored
255 Print a summary of all of the options to `configure', and exit.
256
257 `--help=short'
258 `--help=recursive'
259 Print a summary of the options unique to this package's
260 `configure', and exit. The `short' variant lists options used
261 only in the top level, while the `recursive' variant lists options
262 also present in any nested packages.
62a80c1 @xsisqox Major changes made, so that source code is
authored
263
264 `--version'
265 `-V'
266 Print the version of Autoconf used to generate the `configure'
267 script, and exit.
268
269 `--cache-file=FILE'
270 Enable the cache: use and save the results of the tests in FILE,
271 traditionally `config.cache'. FILE defaults to `/dev/null' to
272 disable caching.
273
274 `--config-cache'
275 `-C'
276 Alias for `--cache-file=config.cache'.
277
278 `--quiet'
279 `--silent'
280 `-q'
281 Do not print messages saying which checks are being made. To
282 suppress all normal output, redirect it to `/dev/null' (any error
283 messages will still be shown).
284
285 `--srcdir=DIR'
286 Look for the package's source code in directory DIR. Usually
287 `configure' can determine that directory automatically.
288
530e891 @xsisqox Update INSTALL
authored
289 `--prefix=DIR'
290 Use DIR as the installation prefix. *Note Installation Names::
291 for more details, including other options available for fine-tuning
292 the installation locations.
293
294 `--no-create'
295 `-n'
296 Run the configure checks, but stop before creating any output
297 files.
298
62a80c1 @xsisqox Major changes made, so that source code is
authored
299 `configure' also accepts some other, not widely useful, options. Run
300 `configure --help' for more details.
301
Something went wrong with that request. Please try again.