Commit | Line | Data |
---|---|---|
6dad9cd3 JB |
1 | Brief Installation Instructions =========================================== |
2 | ||
30d14d55 | 3 | To build Guile on unix, there are two basic steps: |
0196b30a | 4 | |
6dad9cd3 JB |
5 | 1. Type "./configure", to configure the package for your system. |
6 | 2. Type "make", to build the package. | |
0196b30a JB |
7 | |
8 | Generic instructions for configuring and compiling GNU distributions | |
6dad9cd3 JB |
9 | are included below. For Guile, you might type the commands below. |
10 | Their voluminous output is not shown. | |
11 | ||
12 | $ tar xvfz guile-970416.tar.gz # unpack the sources | |
13 | $ cd guile-970416 | |
14 | $ ./configure # adapt Guile to your system | |
15 | $ make # compile Guile | |
16 | $ make install # install in the usual places | |
0196b30a | 17 | |
3bd0adbc JB |
18 | (Note: under SunOS 4.1, you may need to say ./configure --disable-shared; |
19 | Guile's shared library support for that systems seems to be confused.) | |
6dad9cd3 JB |
20 | |
21 | What You Get ============================================================== | |
30d14d55 JB |
22 | |
23 | The `configure' script examines your system, and adapts Guile to | |
24 | compile and run on it. | |
25 | ||
26 | The `make' command builds several things: | |
27 | - An executable file `guile/guile', which is an interactive shell for | |
28 | talking with the Guile Scheme interpreter. | |
6dad9cd3 | 29 | - An object library `libguile/.libs/libguile.a', containing the Guile Scheme |
30d14d55 | 30 | interpreter, ready to be linked into your programs. |
30d14d55 JB |
31 | |
32 | To install Guile, type `make install'. This installs the executable | |
33 | and libraries mentioned above, as well as Guile's header files and | |
34 | Scheme libraries. | |
35 | ||
6dad9cd3 JB |
36 | Make also builds shared libraries, on systems that support them. |
37 | Because of the nature of shared libraries, before linking against | |
38 | them, you should probably install them; `make install' takes care of | |
39 | this. | |
40 | ||
41 | ||
42 | Flags Accepted by Configure =============================================== | |
43 | ||
44 | If you run the configure script with no arguments, it should examine | |
45 | your system and set things up appropriately. However, there are a few | |
46 | switches specific to Guile you may find useful in some circumstances. | |
47 | ||
48 | --enable-maintainer-mode --- If you have automake, autoconf, and | |
49 | libtool installed on your system, this switch causes configure to | |
50 | generate Makefiles which know how to automatically regenerate | |
51 | configure scripts, makefiles, and headers, when they are out of date. | |
52 | The README file says which versions of those tools you will need. | |
53 | ||
54 | --with-threads --- Build a Guile executable and library that supports | |
55 | cooperative threading. If you use this switch, Guile will also build | |
56 | and install the QuickThreads non-preemptive threading library, | |
57 | libqt.a, which you will need to link into your programs after | |
58 | libguile.a. That is, you should pass the switches -lguile -qt to your | |
59 | linker. Coop threads are not yet thoroughly tested; once they are, | |
60 | they will be enabled by default. | |
61 | ||
62 | --enable-dynamic-linking --- Build a Guile executable and library that | |
63 | supports dynamic linking, on systems that support it. This feature is | |
64 | not yet thoroughly tested; once it is, it will be enabled by default. | |
65 | ||
66 | --disable-shared --- Do not build shared libraries. Normally, Guile | |
67 | will build shared libraries if your system supports them. Guile | |
68 | always builds static libraries. | |
69 | ||
70 | ||
71 | Using Guile Without Installing It ========================================= | |
72 | ||
30d14d55 JB |
73 | If you want to run Guile without installing it, set the environment |
74 | variable `SCHEME_LOAD_PATH' to a colon-separated list of directories, | |
75 | including the directory containing this INSTALL file. For example, if | |
76 | you unpacked Guile so that the full filename of this file is | |
cd2e9eb5 | 77 | `/home/jimb/guile-snap/INSTALL', then you might say |
30d14d55 | 78 | |
cd2e9eb5 | 79 | export SCHEME_LOAD_PATH=/home/jimb/my-scheme:/home/jimb/guile-snap |
0196b30a | 80 | |
30d14d55 | 81 | if you're using Bash or any other Bourne shell variant, or |
0196b30a | 82 | |
cd2e9eb5 | 83 | setenv SCHEME_LOAD_PATH /home/jimb/my-scheme:/home/jimb/guile-snap |
0196b30a | 84 | |
30d14d55 | 85 | if you're using CSH or one of its variants. |
0196b30a JB |
86 | |
87 | ||
6dad9cd3 | 88 | Generic Instructions for Building Auto-Configured Packages ================ |
0196b30a JB |
89 | |
90 | To compile this package: | |
91 | ||
92 | 1. Configure the package for your system. In the directory that this | |
93 | file is in, type `./configure'. If you're using `csh' on an old | |
94 | version of System V, you might need to type `sh configure' instead to | |
95 | prevent `csh' from trying to execute `configure' itself. | |
96 | ||
97 | The `configure' shell script attempts to guess correct values for | |
98 | various system-dependent variables used during compilation, and | |
99 | creates the Makefile(s) (one in each subdirectory of the source | |
100 | directory). In some packages it creates a C header file containing | |
101 | system-dependent definitions. It also creates a file `config.status' | |
102 | that you can run in the future to recreate the current configuration. | |
103 | Running `configure' takes a minute or two. | |
104 | ||
105 | To compile the package in a different directory from the one | |
106 | containing the source code, you must use GNU make. `cd' to the | |
107 | directory where you want the object files and executables to go and | |
108 | run `configure' with the option `--srcdir=DIR', where DIR is the | |
109 | directory that contains the source code. Using this option is | |
110 | actually unnecessary if the source code is in the parent directory of | |
111 | the one in which you are compiling; `configure' automatically checks | |
112 | for the source code in `..' if it does not find it in the current | |
113 | directory. | |
114 | ||
115 | By default, `make install' will install the package's files in | |
116 | /usr/local/bin, /usr/local/lib, /usr/local/man, etc. You can specify | |
117 | an installation prefix other than /usr/local by giving `configure' the | |
118 | option `--prefix=PATH'. Alternately, you can do so by changing the | |
119 | `prefix' variable in the Makefile that `configure' creates (the | |
120 | Makefile in the top-level directory, if the package contains | |
121 | subdirectories). | |
122 | ||
123 | You can specify separate installation prefixes for machine-specific | |
124 | files and machine-independent files. If you give `configure' the | |
125 | option `--exec_prefix=PATH', the package will use PATH as the prefix | |
126 | for installing programs and libraries. Normally, all files are | |
127 | installed using the same prefix. | |
128 | ||
129 | `configure' ignores any other arguments that you give it. | |
130 | ||
131 | If your system requires unusual options for compilation or linking | |
132 | that `configure' doesn't know about, you can give `configure' initial | |
133 | values for some variables by setting them in the environment. In | |
134 | Bourne-compatible shells, you can do that on the command line like | |
135 | this: | |
136 | CC='gcc -traditional' DEFS=-D_POSIX_SOURCE ./configure | |
137 | ||
138 | The `make' variables that you might want to override with environment | |
139 | variables when running `configure' are: | |
140 | ||
141 | (For these variables, any value given in the environment overrides the | |
142 | value that `configure' would choose:) | |
143 | CC C compiler program. | |
144 | Default is `cc', or `gcc' if `gcc' is in your PATH. | |
145 | INSTALL Program to use to install files. | |
146 | Default is `install' if you have it, `cp' otherwise. | |
147 | INCLUDEDIR Directory for `configure' to search for include files. | |
148 | Default is /usr/include. | |
149 | ||
150 | (For these variables, any value given in the environment is added to | |
151 | the value that `configure' chooses:) | |
152 | DEFS Configuration options, in the form '-Dfoo -Dbar ...' | |
153 | LIBS Libraries to link with, in the form '-lfoo -lbar ...' | |
154 | ||
155 | If you need to do unusual things to compile the package, we encourage | |
156 | you to teach `configure' how to do them and mail the diffs to the | |
157 | address given in the README so we can include them in the next | |
158 | release. | |
159 | ||
160 | 2. Type `make' to compile the package. | |
161 | ||
162 | 3. Type `make install' to install programs, data files, and | |
163 | documentation. | |
164 | ||
165 | 4. You can remove the program binaries and object files from the | |
166 | source directory by typing `make clean'. To also remove the | |
167 | Makefile(s), the header file containing system-dependent definitions | |
168 | (if the package uses one), and `config.status' (all the files that | |
169 | `configure' created), type `make distclean'. | |
170 | ||
171 | The file `configure.in' is used as a template to create `configure' by | |
172 | a program called `autoconf'. You will only need it if you want to | |
173 | regenerate `configure' using a newer version of `autoconf'. |