Debian Codegraph @

INSTALL

raw
1 Compiling Asymptote from a Source Release
2 =========================================
3
4 To compile and install Asymptote version x.xx from a source release:
5
6 gunzip asymptote-x.xx.src.tgz
7 tar -xf asymptote-x.xx.src.tar
8 cd asymptote-x.xx
9 ./configure
10 make all
11 make install
12
13 The last command requires root privileges. To install without root privileges
14 you should change the first line to
15
16 ./configure --prefix=$HOME/asymptote
17
18 If you get errors from a broken texinfo or pdftex installation, simply put
19 https://asymptote.sourceforge.io/asymptote.pdf
20 in the doc directory and repeat the commands make all and make install.
21
22 For a list of configure options, type
23
24 configure --help
25
26 See also the generic configure instructions below.
27
28 Compiling Asymptote from Git Developmental Source Code
29 =============================================================
30
31 To compile from Git developmental source code:
32
33 git clone https://github.com/vectorgraphics/asymptote
34 cd asymptote
35 ./autogen.sh
36 ./configure
37 make all
38 make install
39
40 Optional packages:
41
42 * Fast Fourier Transform library
43 https://www.fftw.org/
44
45 Version requirement >= 3.0
46
47 * The GNU Scientific Library for numerical analysis:
48 https://www.gnu.org/software/gsl/
49
50 *****************************************
51 Generic Configure Instructions (advanced)
52 *****************************************
53
54 The `configure' shell script attempts to guess correct values for
55 various system-dependent variables used during compilation. It uses
56 those values to create a `Makefile' in each directory of the package.
57 It may also create one or more `.h' files containing system-dependent
58 definitions. Finally, it creates a shell script `config.status' that
59 you can run in the future to recreate the current configuration, and a
60 file `config.log' containing compiler output (useful mainly for
61 debugging `configure').
62
63 It can also use an optional file (typically called `config.cache'
64 and enabled with `--cache-file=config.cache' or simply `-C') that saves
65 the results of its tests to speed up reconfiguring. (Caching is
66 disabled by default to prevent problems with accidental use of stale
67 cache files.)
68
69 If you need to do unusual things to compile the package, please try
70 to figure out how `configure' could check whether to do them, and mail
71 diffs or instructions to the address given in the `README' so they can
72 be considered for the next release. If you are using the cache, and at
73 some point `config.cache' contains results you don't want to keep, you
74 may remove or edit it.
75
76 The file `configure.ac' (or `configure.in') is used to create
77 `configure' by a program called `autoconf'. You only need
78 `configure.ac' if you want to change it or regenerate `configure' using
79 a newer version of `autoconf'.
80
81 The simplest way to compile this package is:
82
83 1. `cd' to the directory containing the package's source code and type
84 `./configure' to configure the package for your system. If you're
85 using `csh' on an old version of System V, you might need to type
86 `sh ./configure' instead to prevent `csh' from trying to execute
87 `configure' itself.
88
89 Running `configure' takes awhile. While running, it prints some
90 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=c89 CFLAGS=-O2 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 must use a version of `make' that
130 supports the `VPATH' variable, such as GNU `make'. `cd' to the
131 directory where you want the object files and executables to go and run
132 the `configure' script. `configure' automatically checks for the
133 source code in the directory that `configure' is in and in `..'.
134
135 If you have to use a `make' that does not support the `VPATH'
136 variable, you have to compile the package for one architecture at a
137 time in the source code directory. After you have installed the
138 package for one architecture, use `make distclean' before reconfiguring
139 for another architecture.
140
141 Installation Names
142 ==================
143
144 By default, `make install' installs the package's commands under
145 `/usr/local/bin', include files under `/usr/local/include', etc. You
146 can specify an installation prefix other than `/usr/local' by giving
147 `configure' the option `--prefix=PREFIX'.
148
149 You can specify separate installation prefixes for
150 architecture-specific files and architecture-independent files. If you
151 pass the option `--exec-prefix=PREFIX' to `configure', the package uses
152 PREFIX as the prefix for installing programs and libraries.
153 Documentation and other data files still use the regular prefix.
154
155 In addition, if you use an unusual directory layout you can give
156 options like `--bindir=DIR' to specify different values for particular
157 kinds of files. Run `configure --help' for a list of the directories
158 you can set and what kinds of files go in them.
159
160 If the package supports it, you can cause programs to be installed
161 with an extra prefix or suffix on their names by giving `configure' the
162 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
163
164 Optional Features
165 =================
166
167 Some packages pay attention to `--enable-FEATURE' options to
168 `configure', where FEATURE indicates an optional part of the package.
169 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
170 is something like `gnu-as' or `x' (for the X Window System). The
171 `README' should mention any `--enable-' and `--with-' options that the
172 package recognizes.
173
174 For packages that use the X Window System, `configure' can usually
175 find the X include and library files automatically, but if it doesn't,
176 you can use the `configure' options `--x-includes=DIR' and
177 `--x-libraries=DIR' to specify their locations.
178
179 Specifying the System Type
180 ==========================
181
182 There may be some features `configure' cannot figure out automatically,
183 but needs to determine by the type of machine the package will run on.
184 Usually, assuming the package is built to be run on the _same_
185 architectures, `configure' can figure that out, but if it prints a
186 message saying it cannot guess the machine type, give it the
187 `--build=TYPE' option. TYPE can either be a short name for the system
188 type, such as `sun4', or a canonical name which has the form:
189
190 CPU-COMPANY-SYSTEM
191
192 where SYSTEM can have one of these forms:
193
194 OS KERNEL-OS
195
196 See the file `config.sub' for the possible values of each field. If
197 `config.sub' isn't included in this package, then this package doesn't
198 need to know the machine type.
199
200 If you are _building_ compiler tools for cross-compiling, you should
201 use the option `--target=TYPE' to select the type of system they will
202 produce code for.
203
204 If you want to _use_ a cross compiler, that generates code for a
205 platform different from the build platform, you should specify the
206 "host" platform (i.e., that on which the generated programs will
207 eventually be run) with `--host=TYPE'.
208
209 Sharing Defaults
210 ================
211
212 If you want to set default values for `configure' scripts to share, you
213 can create a site shell script called `config.site' that gives default
214 values for variables like `CC', `cache_file', and `prefix'.
215 `configure' looks for `PREFIX/share/config.site' if it exists, then
216 `PREFIX/etc/config.site' if it exists. Or, you can set the
217 `CONFIG_SITE' environment variable to the location of the site script.
218 A warning: not all `configure' scripts look for a site script.
219
220 Defining Variables
221 ==================
222
223 Variables not defined in a site shell script can be set in the
224 environment passed to `configure'. However, some packages may run
225 configure again during the build, and the customized values of these
226 variables may be lost. In order to avoid this problem, you should set
227 them in the `configure' command line, using `VAR=value'. For example:
228
229 ./configure CC=/usr/local2/bin/gcc
230
231 causes the specified `gcc' to be used as the C compiler (unless it is
232 overridden in the site shell script). Here is a another example:
233
234 /bin/bash ./configure CONFIG_SHELL=/bin/bash
235
236 Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
237 configuration-related scripts to be executed by `/bin/bash'.
238
239 `configure' Invocation
240 ======================
241
242 `configure' recognizes the following options to control how it operates.
243
244 `--help'
245 `-h'
246 Print a summary of the options to `configure', and exit.
247
248 `--version'
249 `-V'
250 Print the version of Autoconf used to generate the `configure'
251 script, and exit.
252
253 `--cache-file=FILE'
254 Enable the cache: use and save the results of the tests in FILE,
255 traditionally `config.cache'. FILE defaults to `/dev/null' to
256 disable caching.
257
258 `--config-cache'
259 `-C'
260 Alias for `--cache-file=config.cache'.
261
262 `--quiet'
263 `--silent'
264 `-q'
265 Do not print messages saying which checks are being made. To
266 suppress all normal output, redirect it to `/dev/null' (any error
267 messages will still be shown).
268
269 `--srcdir=DIR'
270 Look for the package's source code in directory DIR. Usually
271 `configure' can determine that directory automatically.
272
273 `configure' also accepts some other options. Run
274 `configure --help' for more details.
275