"Fossies" - the Fresh Open Source Software Archive
Member "gtkdatabox-1.0.0/INSTALL" (31 Mar 2021, 9494 Bytes) of package /linux/privat/gtkdatabox-1.0.0.tar.gz:
As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard
) with prefixed line numbers.
Alternatively you can here view
the uninterpreted source code file.
See also the latest Fossies "Diffs"
side-by-side code changes report for "INSTALL": 0.9.3.1_vs_1.0.0
1 Installation Instructions
4 Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
5 2006 Free Software Foundation, Inc.
7 This file is free documentation; the Free Software Foundation gives
8 unlimited permission to copy, distribute and modify it.
10 Basic Installation
13 Briefly, the shell commands `./configure; make; make install' should
14 configure, build, and install this package. The following
15 more-detailed instructions are generic; see the `README' file for
16 instructions specific to this package.
18 If the configure script is missing, run the script : scripts/myAutoreconf.sh
20 The `configure' shell script attempts to guess correct values for
21 various system-dependent variables used during compilation. It uses
22 those values to create a `Makefile' in each directory of the package.
23 It may also create one or more `.h' files containing system-dependent
24 definitions. Finally, it creates a shell script `config.status' that
25 you can run in the future to recreate the current configuration, and a
26 file `config.log' containing compiler output (useful mainly for
27 debugging `configure').
29 It can also use an optional file (typically called `config.cache'
30 and enabled with `--cache-file=config.cache' or simply `-C') that saves
31 the results of its tests to speed up reconfiguring. Caching is
32 disabled by default to prevent problems with accidental use of stale
33 cache files.
35 If you need to do unusual things to compile the package, please try
36 to figure out how `configure' could check whether to do them, and mail
37 diffs or instructions to the address given in the `README' so they can
38 be considered for the next release. If you are using the cache, and at
39 some point `config.cache' contains results you don't want to keep, you
40 may remove or edit it.
42 The file `configure.ac' (or `configure.in') is used to create
43 `configure' by a program called `autoconf'. You need `configure.ac' if
44 you want to change it or regenerate `configure' using a newer version
45 of `autoconf'.
47 The simplest way to compile this package is:
49 1. `cd' to the directory containing the package's source code and type
50 `./configure' to configure the package for your system.
52 Running `configure' might take a while. While running, it prints
53 some messages telling which features it is checking for.
55 2. Type `make' to compile the package.
57 3. Optionally, type `make check' to run any self-tests that come with
58 the package.
60 4. Type `make install' to install the programs and any data files and
63 5. You can remove the program binaries and object files from the
64 source code directory by typing `make clean'. To also remove the
65 files that `configure' created (so you can compile the package for
66 a different kind of computer), type `make distclean'. There is
67 also a `make maintainer-clean' target, but that is intended mainly
68 for the package's developers. If you use it, you may have to get
69 all sorts of other programs in order to regenerate files that came
70 with the distribution.
72 Compilers and Options
75 Some systems require unusual options for compilation or linking that the
76 `configure' script does not know about. Run `./configure --help' for
77 details on some of the pertinent environment variables.
79 You can give `configure' initial values for configuration parameters
80 by setting variables in the command line or in the environment. Here
81 is an example:
83 ./configure CC=c99 CFLAGS=-g LIBS=-lposix
85 *Note Defining Variables::, for more details.
87 Compiling For Multiple Architectures
90 You can compile the package for more than one kind of computer at the
91 same time, by placing the object files for each architecture in their
92 own directory. To do this, you can use GNU `make'. `cd' to the
93 directory where you want the object files and executables to go and run
94 the `configure' script. `configure' automatically checks for the
95 source code in the directory that `configure' is in and in `..'.
97 With a non-GNU `make', it is safer to compile the package for one
98 architecture at a time in the source code directory. After you have
99 installed the package for one architecture, use `make distclean' before
100 reconfiguring for another architecture.
102 Installation Names
105 By default, `make install' installs the package's commands under
106 `/usr/local/bin', include files under `/usr/local/include', etc. You
107 can specify an installation prefix other than `/usr/local' by giving
108 `configure' the option `--prefix=PREFIX'.
110 You can specify separate installation prefixes for
111 architecture-specific files and architecture-independent files. If you
112 pass the option `--exec-prefix=PREFIX' to `configure', the package uses
113 PREFIX as the prefix for installing programs and libraries.
114 Documentation and other data files still use the regular prefix.
116 In addition, if you use an unusual directory layout you can give
117 options like `--bindir=DIR' to specify different values for particular
118 kinds of files. Run `configure --help' for a list of the directories
119 you can set and what kinds of files go in them.
121 If the package supports it, you can cause programs to be installed
122 with an extra prefix or suffix on their names by giving `configure' the
123 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
125 Optional Features
128 Some packages pay attention to `--enable-FEATURE' options to
129 `configure', where FEATURE indicates an optional part of the package.
130 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
131 is something like `gnu-as' or `x' (for the X Window System). The
132 `README' should mention any `--enable-' and `--with-' options that the
133 package recognizes.
135 For packages that use the X Window System, `configure' can usually
136 find the X include and library files automatically, but if it doesn't,
137 you can use the `configure' options `--x-includes=DIR' and
138 `--x-libraries=DIR' to specify their locations.
140 Specifying the System Type
143 There may be some features `configure' cannot figure out automatically,
144 but needs to determine by the type of machine the package will run on.
145 Usually, assuming the package is built to be run on the _same_
146 architectures, `configure' can figure that out, but if it prints a
147 message saying it cannot guess the machine type, give it the
148 `--build=TYPE' option. TYPE can either be a short name for the system
149 type, such as `sun4', or a canonical name which has the form:
153 where SYSTEM can have one of these forms:
155 OS KERNEL-OS
157 See the file `config.sub' for the possible values of each field. If
158 `config.sub' isn't included in this package, then this package doesn't
159 need to know the machine type.
161 If you are _building_ compiler tools for cross-compiling, you should
162 use the option `--target=TYPE' to select the type of system they will
163 produce code for.
165 If you want to _use_ a cross compiler, that generates code for a
166 platform different from the build platform, you should specify the
167 "host" platform (i.e., that on which the generated programs will
168 eventually be run) with `--host=TYPE'.
170 Sharing Defaults
173 If you want to set default values for `configure' scripts to share, you
174 can create a site shell script called `config.site' that gives default
175 values for variables like `CC', `cache_file', and `prefix'.
176 `configure' looks for `PREFIX/share/config.site' if it exists, then
177 `PREFIX/etc/config.site' if it exists. Or, you can set the
178 `CONFIG_SITE' environment variable to the location of the site script.
179 A warning: not all `configure' scripts look for a site script.
181 Defining Variables
184 Variables not defined in a site shell script can be set in the
185 environment passed to `configure'. However, some packages may run
186 configure again during the build, and the customized values of these
187 variables may be lost. In order to avoid this problem, you should set
188 them in the `configure' command line, using `VAR=value'. For example:
190 ./configure CC=/usr/local2/bin/gcc
192 causes the specified `gcc' to be used as the C compiler (unless it is
193 overridden in the site shell script).
195 Unfortunately, this technique does not work for `CONFIG_SHELL' due to
196 an Autoconf bug. Until the bug is fixed you can use this workaround:
198 CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
200 `configure' Invocation
203 `configure' recognizes the following options to control how it operates.
207 Print a summary of the options to `configure', and exit.
211 Print the version of Autoconf used to generate the `configure'
212 script, and exit.
215 Enable the cache: use and save the results of the tests in FILE,
216 traditionally `config.cache'. FILE defaults to `/dev/null' to
217 disable caching.
221 Alias for `--cache-file=config.cache'.
226 Do not print messages saying which checks are being made. To
227 suppress all normal output, redirect it to `/dev/null' (any error
228 messages will still be shown).
231 Look for the package's source code in directory DIR. Usually
232 `configure' can determine that directory automatically.
234 `configure' also accepts some other, not widely useful, options. Run
235 `configure --help' for more details.