Debian Codegraph @

INSTALL

raw
1 Installation Instructions for comptext
2 **************************************
3
4 To compile comptext you will need:
5
6 * A recent C++ compiler. The GNU C++ compilers in the 4.x series are
7 known to work.
8
9 * Version 1.3.x of the Fast Light Tool Kit (FLTK), with its
10 development library and headers. FLTK's multi-threading support is required.
11
12 Once you have installed the required packages, the following commands
13 should be sufficient to compile comptext and install it under /usr/local:
14
15 ./configure
16 make
17 make install (you may need superuser privileges for installation)
18
19 The `install' target installs the executable, an icon, and a .desktop
20 file. After installation, an comptext launcher should appear somewhere in
21 your applications menu.
22
23 Create the desktop launcher. comptext is designed as a desktop application
24 that accepts target files to be wrapped or unwrapped by dropping the
25 file onto the desktop launcher.
26
27 Windows installation notes
28 **************************
29
30 comptext supports win32 systems as a cross compiled application using the
31 MinGW win32 environment.
32
33 To build an internationalized version of comptext, install these
34 additional packages:
35
36 gettext gettext-devel libiconv libiconv2
37
38 ========== Generic installation instructions follow ==========
39
40 Installation Instructions
41 *************************
42
43 Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
44 2006 Free Software Foundation, Inc.
45
46 This file is free documentation; the Free Software Foundation gives
47 unlimited permission to copy, distribute and modify it.
48
49 Basic Installation
50 ==================
51
52 Briefly, the shell commands `./configure; make; make install' should
53 configure, build, and install this package. The following
54 more-detailed instructions are generic; see the `README' file for
55 instructions specific to this package.
56
57 The `configure' shell script attempts to guess correct values for
58 various system-dependent variables used during compilation. It uses
59 those values to create a `Makefile' in each directory of the package.
60 It may also create one or more `.h' files containing system-dependent
61 definitions. Finally, it creates a shell script `config.status' that
62 you can run in the future to recreate the current configuration, and a
63 file `config.log' containing compiler output (useful mainly for
64 debugging `configure').
65
66 It can also use an optional file (typically called `config.cache'
67 and enabled with `--cache-file=config.cache' or simply `-C') that saves
68 the results of its tests to speed up reconfiguring. Caching is
69 disabled by default to prevent problems with accidental use of stale
70 cache files.
71
72 If you need to do unusual things to compile the package, please try
73 to figure out how `configure' could check whether to do them, and mail
74 diffs or instructions to the address given in the `README' so they can
75 be considered for the next release. If you are using the cache, and at
76 some point `config.cache' contains results you don't want to keep, you
77 may remove or edit it.
78
79 The file `configure.ac' (or `configure.in') is used to create
80 `configure' by a program called `autoconf'. You need `configure.ac' if
81 you want to change it or regenerate `configure' using a newer version
82 of `autoconf'.
83
84 The simplest way to compile this package is:
85
86 1. `cd' to the directory containing the package's source code and type
87 `./configure' to configure the package for your system.
88
89 Running `configure' might take a while. While running, it prints
90 some messages telling which features it is checking for.
91
92 2. Type `make' to compile the package.
93
94 3. Optionally, type `make check' to run any self-tests that come with
95 the package.
96
97 4. Type `make install' to install the programs and any data files and
98 documentation.
99
100 5. You can remove the program binaries and object files from the
101 source code directory by typing `make clean'. To also remove the
102 files that `configure' created (so you can compile the package for
103 a different kind of computer), type `make distclean'. There is
104 also a `make maintainer-clean' target, but that is intended mainly
105 for the package's developers. If you use it, you may have to get
106 all sorts of other programs in order to regenerate files that came
107 with the distribution.
108
109 Compilers and Options
110 =====================
111
112 Some systems require unusual options for compilation or linking that the
113 `configure' script does not know about. Run `./configure --help' for
114 details on some of the pertinent environment variables.
115
116 You can give `configure' initial values for configuration parameters
117 by setting variables in the command line or in the environment. Here
118 is an example:
119
120 ./configure CC=c99 CFLAGS=-g LIBS=-lposix
121
122 *Note Defining Variables::, for more details.
123
124 Compiling For Multiple Architectures
125 ====================================
126
127 You can compile the package for more than one kind of computer at the
128 same time, by placing the object files for each architecture in their
129 own directory. To do this, you can use GNU `make'. `cd' to the
130 directory where you want the object files and executables to go and run
131 the `configure' script. `configure' automatically checks for the
132 source code in the directory that `configure' is in and in `..'.
133
134 With a non-GNU `make', it is safer to compile the package for one
135 architecture at a time in the source code directory. After you have
136 installed the package for one architecture, use `make distclean' before
137 reconfiguring for another architecture.
138
139 Installation Names
140 ==================
141
142 By default, `make install' installs the package's commands under
143 `/usr/local/bin', include files under `/usr/local/include', etc. You
144 can specify an installation prefix other than `/usr/local' by giving
145 `configure' the option `--prefix=PREFIX'.
146
147 You can specify separate installation prefixes for
148 architecture-specific files and architecture-independent files. If you
149 pass the option `--exec-prefix=PREFIX' to `configure', the package uses
150 PREFIX as the prefix for installing programs and libraries.
151 Documentation and other data files still use the regular prefix.
152
153 In addition, if you use an unusual directory layout you can give
154 options like `--bindir=DIR' to specify different values for particular
155 kinds of files. Run `configure --help' for a list of the directories
156 you can set and what kinds of files go in them.
157
158 If the package supports it, you can cause programs to be installed
159 with an extra prefix or suffix on their names by giving `configure' the
160 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
161
162 Optional Features
163 =================
164
165 Some packages pay attention to `--enable-FEATURE' options to
166 `configure', where FEATURE indicates an optional part of the package.
167 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
168 is something like `gnu-as' or `x' (for the X Window System). The
169 `README' should mention any `--enable-' and `--with-' options that the
170 package recognizes.
171
172 For packages that use the X Window System, `configure' can usually
173 find the X include and library files automatically, but if it doesn't,
174 you can use the `configure' options `--x-includes=DIR' and
175 `--x-libraries=DIR' to specify their locations.
176
177 Specifying the System Type
178 ==========================
179
180 There may be some features `configure' cannot figure out automatically,
181 but needs to determine by the type of machine the package will run on.
182 Usually, assuming the package is built to be run on the _same_
183 architectures, `configure' can figure that out, but if it prints a
184 message saying it cannot guess the machine type, give it the
185 `--build=TYPE' option. TYPE can either be a short name for the system
186 type, such as `sun4', or a canonical name which has the form:
187
188 CPU-COMPANY-SYSTEM
189
190 where SYSTEM can have one of these forms:
191
192 OS KERNEL-OS
193
194 See the file `config.sub' for the possible values of each field. If
195 `config.sub' isn't included in this package, then this package doesn't
196 need to know the machine type.
197
198 If you are _building_ compiler tools for cross-compiling, you should
199 use the option `--target=TYPE' to select the type of system they will
200 produce code for.
201
202 If you want to _use_ a cross compiler, that generates code for a
203 platform different from the build platform, you should specify the
204 "host" platform (i.e., that on which the generated programs will
205 eventually be run) with `--host=TYPE'.
206
207 Sharing Defaults
208 ================
209
210 If you want to set default values for `configure' scripts to share, you
211 can create a site shell script called `config.site' that gives default
212 values for variables like `CC', `cache_file', and `prefix'.
213 `configure' looks for `PREFIX/share/config.site' if it exists, then
214 `PREFIX/etc/config.site' if it exists. Or, you can set the
215 `CONFIG_SITE' environment variable to the location of the site script.
216 A warning: not all `configure' scripts look for a site script.
217
218 Defining Variables
219 ==================
220
221 Variables not defined in a site shell script can be set in the
222 environment passed to `configure'. However, some packages may run
223 configure again during the build, and the customized values of these
224 variables may be lost. In order to avoid this problem, you should set
225 them in the `configure' command line, using `VAR=value'. For example:
226
227 ./configure CC=/usr/local2/bin/gcc
228
229 causes the specified `gcc' to be used as the C compiler (unless it is
230 overridden in the site shell script).
231
232 Unfortunately, this technique does not work for `CONFIG_SHELL' due to
233 an Autoconf bug. Until the bug is fixed you can use this workaround:
234
235 CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
236
237 `configure' Invocation
238 ======================
239
240 `configure' recognizes the following options to control how it operates.
241
242 `--help'
243 `-h'
244 Print a summary of the options to `configure', and exit.
245
246 `--version'
247 `-V'
248 Print the version of Autoconf used to generate the `configure'
249 script, and exit.
250
251 `--cache-file=FILE'
252 Enable the cache: use and save the results of the tests in FILE,
253 traditionally `config.cache'. FILE defaults to `/dev/null' to
254 disable caching.
255
256 `--config-cache'
257 `-C'
258 Alias for `--cache-file=config.cache'.
259
260 `--quiet'
261 `--silent'
262 `-q'
263 Do not print messages saying which checks are being made. To
264 suppress all normal output, redirect it to `/dev/null' (any error
265 messages will still be shown).
266
267 `--srcdir=DIR'
268 Look for the package's source code in directory DIR. Usually
269 `configure' can determine that directory automatically.
270
271 `configure' also accepts some other, not widely useful, options. Run
272 `configure --help' for more details.
273