1 Installation Instructions
2 *************************
6 Aspectbin includes support for integration with the Glade user interface
7 builder. This support will be compiled in if libgladeui is detected during the
8 configure process, and can be controlled by the --with-gladeui option.
10 However, proper installation of the Glade UI components requires that Glade and
11 Aspectbin are installed to the same prefix. If they are not, then the glade
12 components will not be installed to the proper locations. If you must install
13 to a different prefix, it is still possible to use the component with the Glade
14 UI by setting the GLADE_MODULE_PATH and GLADE_CATALOG_PATH environment
20 Briefly, the shell commands `./configure; make; make install' should
21 configure, build, and install this package. The following
22 more-detailed instructions are generic; see the `README' file for
23 instructions specific to this package.
25 The `configure' shell script attempts to guess correct values for
26 various system-dependent variables used during compilation. It uses
27 those values to create a `Makefile' in each directory of the package.
28 It may also create one or more `.h' files containing system-dependent
29 definitions. Finally, it creates a shell script `config.status' that
30 you can run in the future to recreate the current configuration, and a
31 file `config.log' containing compiler output (useful mainly for
32 debugging `configure').
34 It can also use an optional file (typically called `config.cache'
35 and enabled with `--cache-file=config.cache' or simply `-C') that saves
36 the results of its tests to speed up reconfiguring. Caching is
37 disabled by default to prevent problems with accidental use of stale
40 If you need to do unusual things to compile the package, please try
41 to figure out how `configure' could check whether to do them, and mail
42 diffs or instructions to the address given in the `README' so they can
43 be considered for the next release. If you are using the cache, and at
44 some point `config.cache' contains results you don't want to keep, you
45 may remove or edit it.
47 The file `configure.ac' (or `configure.in') is used to create
48 `configure' by a program called `autoconf'. You need `configure.ac' if
49 you want to change it or regenerate `configure' using a newer version
52 The simplest way to compile this package is:
54 1. `cd' to the directory containing the package's source code and type
55 `./configure' to configure the package for your system.
57 Running `configure' might take a while. While running, it prints
58 some messages telling which features it is checking for.
60 2. Type `make' to compile the package.
62 3. Optionally, type `make check' to run any self-tests that come with
65 4. Type `make install' to install the programs and any data files and
68 5. You can remove the program binaries and object files from the
69 source code directory by typing `make clean'. To also remove the
70 files that `configure' created (so you can compile the package for
71 a different kind of computer), type `make distclean'. There is
72 also a `make maintainer-clean' target, but that is intended mainly
73 for the package's developers. If you use it, you may have to get
74 all sorts of other programs in order to regenerate files that came
75 with the distribution.
77 6. Often, you can also type `make uninstall' to remove the installed
83 Some systems require unusual options for compilation or linking that
84 the `configure' script does not know about. Run `./configure --help'
85 for details on some of the pertinent environment variables.
87 You can give `configure' initial values for configuration parameters
88 by setting variables in the command line or in the environment. Here
91 ./configure CC=c99 CFLAGS=-g LIBS=-lposix
93 *Note Defining Variables::, for more details.
95 Compiling For Multiple Architectures
96 ====================================
98 You can compile the package for more than one kind of computer at the
99 same time, by placing the object files for each architecture in their
100 own directory. To do this, you can use GNU `make'. `cd' to the
101 directory where you want the object files and executables to go and run
102 the `configure' script. `configure' automatically checks for the
103 source code in the directory that `configure' is in and in `..'.
105 With a non-GNU `make', it is safer to compile the package for one
106 architecture at a time in the source code directory. After you have
107 installed the package for one architecture, use `make distclean' before
108 reconfiguring for another architecture.
110 On MacOS X 10.5 and later systems, you can create libraries and
111 executables that work on multiple system types--known as "fat" or
112 "universal" binaries--by specifying multiple `-arch' options to the
113 compiler but only a single `-arch' option to the preprocessor. Like
116 ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
117 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
118 CPP="gcc -E" CXXCPP="g++ -E"
120 This is not guaranteed to produce working output in all cases, you
121 may have to build one architecture at a time and combine the results
122 using the `lipo' tool if you have problems.
127 By default, `make install' installs the package's commands under
128 `/usr/local/bin', include files under `/usr/local/include', etc. You
129 can specify an installation prefix other than `/usr/local' by giving
130 `configure' the option `--prefix=PREFIX'.
132 You can specify separate installation prefixes for
133 architecture-specific files and architecture-independent files. If you
134 pass the option `--exec-prefix=PREFIX' to `configure', the package uses
135 PREFIX as the prefix for installing programs and libraries.
136 Documentation and other data files still use the regular prefix.
138 In addition, if you use an unusual directory layout you can give
139 options like `--bindir=DIR' to specify different values for particular
140 kinds of files. Run `configure --help' for a list of the directories
141 you can set and what kinds of files go in them.
143 If the package supports it, you can cause programs to be installed
144 with an extra prefix or suffix on their names by giving `configure' the
145 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
150 Some packages pay attention to `--enable-FEATURE' options to
151 `configure', where FEATURE indicates an optional part of the package.
152 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
153 is something like `gnu-as' or `x' (for the X Window System). The
154 `README' should mention any `--enable-' and `--with-' options that the
157 For packages that use the X Window System, `configure' can usually
158 find the X include and library files automatically, but if it doesn't,
159 you can use the `configure' options `--x-includes=DIR' and
160 `--x-libraries=DIR' to specify their locations.
165 On HP-UX, the default C compiler is not ANSI C compatible. If GNU
166 CC is not installed, it is recommended to use the following options in
167 order to use an ANSI C compiler:
169 ./configure CC="cc -Ae"
171 and if that doesn't work, install pre-built binaries of GCC for HP-UX.
173 On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
174 parse its `<wchar.h>' header file. The option `-nodtk' can be used as
175 a workaround. If GNU CC is not installed, it is therefore recommended
180 and if that doesn't work, try
182 ./configure CC="cc -nodtk"
184 Specifying the System Type
185 ==========================
187 There may be some features `configure' cannot figure out
188 automatically, but needs to determine by the type of machine the package
189 will run on. Usually, assuming the package is built to be run on the
190 _same_ architectures, `configure' can figure that out, but if it prints
191 a message saying it cannot guess the machine type, give it the
192 `--build=TYPE' option. TYPE can either be a short name for the system
193 type, such as `sun4', or a canonical name which has the form:
197 where SYSTEM can have one of these forms:
201 See the file `config.sub' for the possible values of each field. If
202 `config.sub' isn't included in this package, then this package doesn't
203 need to know the machine type.
205 If you are _building_ compiler tools for cross-compiling, you should
206 use the option `--target=TYPE' to select the type of system they will
209 If you want to _use_ a cross compiler, that generates code for a
210 platform different from the build platform, you should specify the
211 "host" platform (i.e., that on which the generated programs will
212 eventually be run) with `--host=TYPE'.
217 If you want to set default values for `configure' scripts to share,
218 you can create a site shell script called `config.site' that gives
219 default values for variables like `CC', `cache_file', and `prefix'.
220 `configure' looks for `PREFIX/share/config.site' if it exists, then
221 `PREFIX/etc/config.site' if it exists. Or, you can set the
222 `CONFIG_SITE' environment variable to the location of the site script.
223 A warning: not all `configure' scripts look for a site script.
228 Variables not defined in a site shell script can be set in the
229 environment passed to `configure'. However, some packages may run
230 configure again during the build, and the customized values of these
231 variables may be lost. In order to avoid this problem, you should set
232 them in the `configure' command line, using `VAR=value'. For example:
234 ./configure CC=/usr/local2/bin/gcc
236 causes the specified `gcc' to be used as the C compiler (unless it is
237 overridden in the site shell script).
239 Unfortunately, this technique does not work for `CONFIG_SHELL' due to
240 an Autoconf bug. Until the bug is fixed you can use this workaround:
242 CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
244 `configure' Invocation
245 ======================
247 `configure' recognizes the following options to control how it
252 Print a summary of all of the options to `configure', and exit.
256 Print a summary of the options unique to this package's
257 `configure', and exit. The `short' variant lists options used
258 only in the top level, while the `recursive' variant lists options
259 also present in any nested packages.
263 Print the version of Autoconf used to generate the `configure'
267 Enable the cache: use and save the results of the tests in FILE,
268 traditionally `config.cache'. FILE defaults to `/dev/null' to
273 Alias for `--cache-file=config.cache'.
278 Do not print messages saying which checks are being made. To
279 suppress all normal output, redirect it to `/dev/null' (any error
280 messages will still be shown).
283 Look for the package's source code in directory DIR. Usually
284 `configure' can determine that directory automatically.
287 Use DIR as the installation prefix. *Note Installation Names::
288 for more details, including other options available for fine-tuning
289 the installation locations.
293 Run the configure checks, but stop before creating any output
296 `configure' also accepts some other, not widely useful, options. Run
297 `configure --help' for more details.