diff options
author | Jim Ramsay <i.am@jimramsay.com> | 2010-08-10 15:07:50 (GMT) |
---|---|---|
committer | Jim Ramsay <i.am@jimramsay.com> | 2010-08-10 15:46:11 (GMT) |
commit | bf0d2565860990f5f177d48919fc5990e1602094 (patch) | |
tree | 72f0f3f9534d5c447588990c4a67fde389f3268d /INSTALL | |
parent | 0cc08f90d2d46b6467e06e16bb3d4c740b6c2cc5 (diff) | |
download | fluxbox_pavel-bf0d2565860990f5f177d48919fc5990e1602094.zip fluxbox_pavel-bf0d2565860990f5f177d48919fc5990e1602094.tar.bz2 |
Removing more autoconf-generated files
There is no need to keep INSTALL, install-sh, ltconfig, mkinstalldirs in git, as
they can be created by 'automake -a -c' as needed.
In fact, it turns out ltconfig and mkinstalldirs are not needed at all any more.
Diffstat (limited to 'INSTALL')
-rw-r--r-- | INSTALL | 90 |
1 files changed, 0 insertions, 90 deletions
diff --git a/INSTALL b/INSTALL deleted file mode 100644 index ee8983e..0000000 --- a/INSTALL +++ /dev/null | |||
@@ -1,90 +0,0 @@ | |||
1 | -- INSTALL for Fluxbox | ||
2 | |||
3 | Compilation and Installation: | ||
4 | -------------------------------- | ||
5 | The `configure' shell script attempts to guess correct values for | ||
6 | various system-dependent variables used during compilation. It uses | ||
7 | those values to create a `Makefile' in each directory in the | ||
8 | Fluxbox source tree. | ||
9 | |||
10 | Finally, it creates a shell script `config.status' that you can run | ||
11 | in the future to recreate the current configuration, a file | ||
12 | `config.cache' that saves the results of its tests to speed up | ||
13 | reconfiguring, and a file `config.log' containing compiler output | ||
14 | (useful mainly for debugging `configure'). | ||
15 | |||
16 | If you need to do unusual things to compile Fluxbox, please try | ||
17 | to figure out how `configure' could check whether to do them, and mail | ||
18 | diffs or instructions to fluxbox-developers list (see www.fluxbox.org) | ||
19 | so they can be considered for the next release. If at some point | ||
20 | `config.cache' contains results you don't want to keep, you may remove | ||
21 | or edit it. | ||
22 | |||
23 | The file `configure.in' is used to create `configure' by a program | ||
24 | called `autoconf'. You only need `configure.in' if you want to change | ||
25 | it or regenerate `configure' using a newer version of `autoconf'. | ||
26 | |||
27 | The simplest way to compile this package is: | ||
28 | |||
29 | 1. `cd' to the directory containing the package's source code and type | ||
30 | `./configure' to configure the package for your system. If you're | ||
31 | using `csh' on an old version of System V, you might need to type | ||
32 | `sh ./configure' instead to prevent `csh' from trying to execute | ||
33 | `configure' itself. | ||
34 | |||
35 | Running `configure' takes awhile. While running, it prints some | ||
36 | messages telling which features it is checking for. | ||
37 | |||
38 | 2. Type `make' to compile the package. | ||
39 | |||
40 | 3. Type `make install' to install the programs and any data files and | ||
41 | documentation. | ||
42 | |||
43 | 4. You can remove the program binaries and object files from the | ||
44 | source code directory by typing `make clean'. To also remove the | ||
45 | files that `configure' created (so you can compile the package for | ||
46 | a different kind of computer), type `make distclean'. | ||
47 | |||
48 | |||
49 | Compilers and Options: | ||
50 | ---------------------- | ||
51 | Some systems require unusual options for compilation or linking that | ||
52 | the `configure' script does not know about. You can give `configure' | ||
53 | initial values for variables by setting them in the environment. Using | ||
54 | a Bourne-compatible shell, you can do that on the command line like | ||
55 | this: | ||
56 | CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure | ||
57 | |||
58 | Or on systems that have the `env' program, you can do it like this: | ||
59 | env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure | ||
60 | |||
61 | |||
62 | Optional Features: | ||
63 | ------------------ | ||
64 | Fluxbox supports the XShape extension of X11R6. This support is enabled by | ||
65 | default, but may be overridden by specifying `--disable-shape' on the configure | ||
66 | script's command line. | ||
67 | |||
68 | Fluxbox supports Window Maker dockapps (warning: restarts from wmaker to | ||
69 | fluxbox don't always handle dockapps correctly) with a gadget called the Slit. | ||
70 | The Slit is compiled into Fluxbox by default, but may be overridden by | ||
71 | specifying `--disable-slit' on the configure script's command line. | ||
72 | |||
73 | Fluxbox supports a rendering effect called "faked interlacing" which darkens | ||
74 | every other line in rendered images. This support works only for gradient | ||
75 | images. It is compiled in by default, but may be overridden by specifying | ||
76 | `--disable-interlace' on the configure script's command line. | ||
77 | |||
78 | Fluxbox uses a timer which allows it to periodically flush its pixmap | ||
79 | cache. It is enabled by default, but may be overridden by specifying | ||
80 | '--disable-timed-cache' on the configure script's command line. | ||
81 | |||
82 | Also, `configure' can usually find the X include and library files | ||
83 | automatically, but if it doesn't, you can use the `configure' | ||
84 | options `--x-includes=DIR' and `--x-libraries=DIR' to specify | ||
85 | their locations. | ||
86 | |||
87 | |||
88 | Please read the README file also. | ||
89 | |||
90 | |||