Next: Editing a configuration
Up: Configuring LiDIA
Previous: Creating a new
We will now describe the variables contained in the configuration
file created in section
.
- LIDIA_HOME
This is the location of LiDIA
after the unpacking
procedure. In our example this would be
/home/mydir/LiDIA or d:
- LIDIA_INSTALL_DIR
This is the directory where the library and include
files of LiDIA
are to be installed in. We
recommend that you use a standard directory which is
searched by default by the linker, i.e., /usr/local.
For OS/2 -- systems using emx we recommend to either use a
standard directory like d:
emx or
-- better in our opinion -- to update the Paths in config.sys:
Add d:/LiDIA/include to C_INCLUDE_PATH and
CPLUS_INCLUDE_PATH and add
d:/LiDIA/lib/LiDIA/os2/compiler_name to LIBRARY_PATH.
- LIDIA_ARCH
This is the destination architecture of LiDIA
. To
allow the installation of LiDIA
on different
machines in a single directory (i.e. /usr/local),
the installation procedure copies LiDIA
's library into the directory
LIDIA_INSTALL_DIR/lib/LiDIA/LIDIA_ARCH/compiler_name
For example, for the architecture sparc7 a directory
/usr/local/lib/LiDIA/sparc7/compiler_name
would be created and LiDIA
's sparc7-compiled library would
be put into this directory.
- LIDIA_TARGET
For known architectures (or in other words, architectures for which
we have assembly support) LIDIA_TARGET is eual to LIDIA_ARCH. In all
other cases, it is set to C, that is LiDIA
will compile the C version
of the kernel.
- BIGINT
This is used to decide which integer arithmetic is to be compiled with
LiDIA
. At the moment we support two possibilities: libI (the
default) and lip. We suggest that you use the default on all
known architectures and lip whenever LIDIA_TARGET is set to C
by configure.
- GMM
LiDIA
's general memory manager can be also replaced by any other one
supporting its interface. At the moment we support only one memory
manager.
- CC
This variable holds the C compiler. This could be one of
SunOS cc
, GNUS's gcc
or any
ANSI
C compiler.
(If you want to use the gcc compiler with the AT&T CC
compiler please set the environment variable ccC,
for example by typing in your csh
setenv ccC /usr/local/bin/gcc.)
- CPP
This variable holds the C++
compiler. This could be one of
AT&T's CC
, GNUS's g++
or any ANSI C++ compiler
.
- CFLAGS
These are the flags for the C compiler.
- CPPFLAGS
These are the flags for the C++
compiler.
- LDFLAGS
These are the flags for the loader.
- AS
This variable holds the assembler. Note LiDIA
's assembler
must understand the -P (preprocessor) option (i.e. use
/bin/as or /usr/bin/as)
- RANLIB
This is the Unix ranlib command. It does not exist
on all operating systems (e.g non- BSD
); in this
case it should be defined to echo.
- KERNEL_FLAGS
This variable allows additional flags for the C-kernel
of LiDIA
that are not needed on the higher levels.
- HAS_RANDOM
This variable is set to random.o if no random number
function is defined on your system.
For an example of a configuration file, see
UnpackDir/LiDIA/config/CONFIG.
Next: Editing a configuration
Up: Configuring LiDIA
Previous: Creating a new
LiDIA Administrator
Thu Aug 10 16:41:08 MET DST 1995