|
70
by Curtis Hovey
Added i18n. |
1 |
Installation Instructions |
2 |
*************************
|
|
3 |
||
4 |
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free |
|
5 |
Software Foundation, Inc. |
|
6 |
||
7 |
This file is free documentation; the Free Software Foundation gives |
|
8 |
unlimited permission to copy, distribute and modify it. |
|
9 |
||
10 |
Basic Installation |
|
11 |
==================
|
|
12 |
||
13 |
These are generic installation instructions. |
|
14 |
||
15 |
The `configure' shell script attempts to guess correct values for |
|
16 |
various system-dependent variables used during compilation. It uses |
|
17 |
those values to create a `Makefile' in each directory of the package. |
|
18 |
It may also create one or more `.h' files containing system-dependent |
|
19 |
definitions. Finally, it creates a shell script `config.status' that |
|
20 |
you can run in the future to recreate the current configuration, and a |
|
21 |
file `config.log' containing compiler output (useful mainly for |
|
22 |
debugging `configure'). |
|
23 |
||
24 |
It can also use an optional file (typically called `config.cache' |
|
25 |
and enabled with `--cache-file=config.cache' or simply `-C') that saves |
|
26 |
the results of its tests to speed up reconfiguring. (Caching is |
|
27 |
disabled by default to prevent problems with accidental use of stale |
|
28 |
cache files.) |
|
29 |
||
30 |
If you need to do unusual things to compile the package, please try |
|
31 |
to figure out how `configure' could check whether to do them, and mail |
|
32 |
diffs or instructions to the address given in the `README' so they can |
|
33 |
be considered for the next release. If you are using the cache, and at |
|
34 |
some point `config.cache' contains results you don't want to keep, you |
|
35 |
may remove or edit it. |
|
36 |
||
37 |
The file `configure.ac' (or `configure.in') is used to create |
|
38 |
`configure' by a program called `autoconf'. You only need |
|
39 |
`configure.ac' if you want to change it or regenerate `configure' using |
|
40 |
a newer version of `autoconf'. |
|
41 |
||
42 |
The simplest way to compile this package is: |
|
43 |
||
44 |
1. `cd' to the directory containing the package's source code and type |
|
45 |
`./configure' to configure the package for your system. If you're |
|
46 |
using `csh' on an old version of System V, you might need to type |
|
47 |
`sh ./configure' instead to prevent `csh' from trying to execute |
|
48 |
`configure' itself. |
|
49 |
||
50 |
Running `configure' takes awhile. While running, it prints some |
|
51 |
messages telling which features it is checking for. |
|
52 |
||
53 |
2. Type `make' to compile the package. |
|
54 |
||
55 |
3. Optionally, type `make check' to run any self-tests that come with |
|
56 |
the package. |
|
57 |
||
58 |
4. Type `make install' to install the programs and any data files and |
|
59 |
documentation. |
|
60 |
||
61 |
5. You can remove the program binaries and object files from the |
|
62 |
source code directory by typing `make clean'. To also remove the |
|
63 |
files that `configure' created (so you can compile the package for |
|
64 |
a different kind of computer), type `make distclean'. There is |
|
65 |
also a `make maintainer-clean' target, but that is intended mainly |
|
66 |
for the package's developers. If you use it, you may have to get |
|
67 |
all sorts of other programs in order to regenerate files that came |
|
68 |
with the distribution. |
|
69 |
||
|
206
by sinzui
Updated docs. |
70 |
Gedit Plugin Installation |
71 |
=========================
|
|
72 |
||
73 |
To install the plugins for personal use (in your home directory), |
|
74 |
run the following commands from a terminal: |
|
75 |
||
76 |
./configure |
|
77 |
make
|
|
78 |
make install |
|
79 |
||
80 |
Or you may choose to install the plugins in another location. |
|
81 |
||
82 |
./configure --without-home --prefix=</path/to/location> |
|
83 |
make
|
|
84 |
make install |
|
85 |
||
86 |
To install the plugins in the same location as the standard |
|
87 |
gedit plugins, set the prefix path to the same as gedit (usually |
|
88 |
/usr). |
|
|
70
by Curtis Hovey
Added i18n. |
89 |
|
|
251
by sinzui
Removed unused files from build. |
90 |
configure' Invocation |
91 |
=====================
|
|
|
70
by Curtis Hovey
Added i18n. |
92 |
|
93 |
`configure' recognizes the following options to control how it operates. |
|
94 |
||
95 |
`--help' |
|
96 |
`-h' |
|
97 |
Print a summary of the options to `configure', and exit. |
|
98 |
||
99 |
`--version' |
|
100 |
`-V' |
|
101 |
Print the version of Autoconf used to generate the `configure' |
|
102 |
script, and exit. |
|
103 |
||
104 |
`--cache-file=FILE' |
|
105 |
Enable the cache: use and save the results of the tests in FILE, |
|
106 |
traditionally `config.cache'. FILE defaults to `/dev/null' to |
|
107 |
disable caching. |
|
108 |
||
109 |
`--config-cache' |
|
110 |
`-C' |
|
111 |
Alias for `--cache-file=config.cache'. |
|
112 |
||
113 |
`--quiet' |
|
114 |
`--silent' |
|
115 |
`-q' |
|
116 |
Do not print messages saying which checks are being made. To |
|
117 |
suppress all normal output, redirect it to `/dev/null' (any error |
|
118 |
messages will still be shown). |
|
119 |
||
120 |
`--srcdir=DIR' |
|
121 |
Look for the package's source code in directory DIR. Usually |
|
122 |
`configure' can determine that directory automatically. |
|
123 |
||
124 |
`configure' also accepts some other, not widely useful, options. Run |
|
125 |
`configure --help' for more details. |
|
126 |