Commit | Line | Data |
---|---|---|
9230f138 C |
1 | 1. Get a C++ compiler. The C++ source files use a suffix of `.cc', so |
2 | your C++ compiler must be able to handle this. If you don't already | |
3 | have a C++ compiler, I suggest gcc 2.3.1 or later (gcc version 2 | |
4 | includes GNU C++ as well as GNU C). If you are using gcc or g++ as | |
5 | your C++ compiler, you will also need to install the corresponding | |
6 | version of libg++, unless your system header files provide C++ | |
7 | support. | |
8 | ||
9 | 2. In the directory that this file is in, type `./configure'. If | |
10 | you're using `csh' on an old version of System V, you might need to | |
11 | type `sh configure' instead to prevent `csh' from trying to execute | |
12 | `configure' itself. | |
13 | ||
14 | The `configure' shell script attempts to guess correct values for | |
15 | various system-dependent variables used during compilation, and | |
16 | creates the Makefile. It also creates a file `config.status' that you | |
17 | can run in the future to recreate the current configuration. | |
18 | ||
19 | Running `configure' takes a minute or two. While it is running, it | |
20 | prints some messages that tell what it is doing. It also performs | |
21 | some checks on your C++ compiler. If these checks fail, it will print | |
22 | a message and exit. In this case, you should correct the problems | |
23 | with your C++ compiler and then rerun configure. | |
24 | ||
25 | To compile the package in a different directory from the one | |
26 | containing the source code, you must use GNU make (or a version of | |
27 | make that supports VPATH in the same way as GNU make). `cd' to the | |
28 | directory where you want the object files and executables to go and | |
29 | run `configure'. `configure' automatically checks for the source code | |
30 | in the directory that `configure' is in and in `..'. If for some | |
31 | reason `configure' is not in the source code directory that you are | |
32 | configuring, then it will report that it can't find the source code. | |
33 | In that case, run `configure' with the option `--srcdir=DIR', where | |
34 | DIR is the directory that contains the source code. | |
35 | ||
36 | By default, `make install' will install the package's files in | |
37 | /usr/local/bin, /usr/local/lib/groff, and /usr/local/man. You can | |
38 | specify an installation prefix other than /usr/local by giving | |
39 | `configure' the option `--prefix=PATH'. Alternately, you can do so by | |
40 | changing the `prefix' variable in the Makefile that `configure' | |
41 | creates. | |
42 | ||
43 | You can specify separate installation prefixes for | |
44 | architecture-specific files and architecture-independent files. If | |
45 | you give `configure' the option `--exec_prefix=PATH', the package will | |
46 | use PATH as the prefix for installing programs and libraries. Data | |
47 | files and documentation will still use the regular prefix. Normally, | |
48 | all files are installed using the regular prefix. | |
49 | ||
50 | You can tell `configure' to figure out the configuration for your | |
51 | system, and record it in `config.status', without actually configuring | |
52 | the package (creating `Makefile's and perhaps a configuration header | |
53 | file). To do this, give `configure' the `--no-create' option. Later, | |
54 | you can run `./config.status' to actually configure the package. This | |
55 | option is useful mainly in `Makefile' rules for updating `config.status' | |
56 | and `Makefile'. You can also give `config.status' the `--recheck' | |
57 | option, which makes it re-run `configure' with the same arguments you | |
58 | used before. This is useful if you change `configure'. | |
59 | ||
60 | `configure' ignores any other arguments that you give it. | |
61 | ||
62 | If your system requires unusual options for compilation or linking | |
63 | that `configure' doesn't know about, you can give `configure' initial | |
64 | values for some variables by setting them in the environment. In | |
65 | Bourne-compatible shells, you can do that on the command line like | |
66 | this: | |
67 | CC='gcc -traditional' DEFS=-D_POSIX_SOURCE ./configure | |
68 | ||
69 | The `make' variables that you might want to override with environment | |
70 | variables when running `configure' are: | |
71 | ||
72 | (For these variables, any value given in the environment overrides the | |
73 | value that `configure' would choose:) | |
74 | CC C compiler program. | |
75 | Default is `cc', or `gcc' if `gcc' is in your PATH. | |
76 | CCC C++ compiler program (for .cc files). | |
77 | By default, configure will look for gcc version 2, g++, | |
78 | and then CC. | |
79 | INSTALL Program to use to install files. | |
80 | Default is `install' if you have it, `cp' otherwise. | |
81 | PAGE This should be `A4' if your PostScript printer uses | |
82 | A4 paper and `letter' if your printer uses 8.5x11in | |
83 | paper. | |
84 | ||
85 | (For these variables, any value given in the environment is added to | |
86 | the value that `configure' chooses:) | |
87 | DEFS Configuration options, in the form `-Dfoo -Dbar ...' | |
88 | LIBS Libraries to link with, in the form `-lfoo -lbar ...' | |
89 | CCLIBS Libraries to link C++ programs with, in the same form. | |
90 | ||
91 | ||
92 | If you need to do unusual things to compile the package, we encourage | |
93 | you to figure out how `configure' could check whether to do them, and | |
94 | mail diffs or instructions to the address given in the README so we | |
95 | can include them in the next release. | |
96 | ||
97 | 3. Have a look at the generated Makefile. The options you are most | |
98 | likely to want to change are near the beginning. Make sure that the | |
99 | definition of PAGE is correct. | |
100 | ||
101 | 4. Type `make'. | |
102 | ||
103 | 5. Use the test-groff script to try groff out on one of the man pages. | |
104 | (Use the .n files not the .man files.) The test-groff script sets up | |
105 | environment variables to allow groff to run without being installed. | |
106 | The current directory must be the build directory when the script is | |
107 | run. For example, you could do | |
108 | ||
109 | ./test-groff -man -Tascii groff/groff.n | less | |
110 | ||
111 | 6. If you want to install gxditview (an X11 previewer), follow the | |
112 | instructions in the INSTALL file in the xditview directory. | |
113 | ||
114 | 7. Type `make install' to install groff. | |
115 | ||
116 | 8. Try the installed version of groff on one of the man pages. | |
117 | ||
118 | If you have problems, read the PROBLEMS file. If this doesn't help | |
119 | send a bug report using the form in the file BUG-REPORT. |