# Introduction

This chapter describes the installation procedures for the programming language distribution. This chapter explains how to set and compile this distribution.

## AFNIX distribution

can be downloaded from the AFNIX home page. The result is complete source tree that is ready for compilation. The distribution contains also the documentation as well as examples. The distribution is supported on a variety of platforms as indicated below that can be either 32 bits or 64 bits machines. The language is also distributed by FreeBSD.

## AFNIX supported platforms

Platform | Processor | Operating system
Linux | IA32, IA64, X86/64, Alpha, M68K, SPARC, PPC, ARM and MIPS | Linux 2.4 and 2.6
FreeBSD | IA32, IA64, X86/64, SPARC, SPARC64 | FreeBSD 4.x, 5.x, 6.x
Darwin | PPC, IA32 | MacOS X 10.4
Solaris | SPARC V7, ULTRASPARC V9 | Solaris 2.7 and 2.8

## Installation procedure

is written in C++. has been successfully built with the `GNU GCC 3` and `GCC 4`. No other compiler have been tested. You will also need the `GNU Make` package. With some distributions the command is called `gmake`. Note that the Makefile hierarchy is designed to operate safely with the `-j` `GNU Make` option.

## Unpacking the distribution

The distribution is available as a compressed tar file. Note that the documentation is distributed in a separate file. The following command unpacks the distribution.

zsh> gzip -d afnix-src-[version].tar.gz zsh> tar xf afnix-src-[version].tar

## Quick command reference

The list of commands to execute is given in the example below. A detailed description for each command is given hereafter. The `make world` is the default command that builds the whole tree with the default compiler.

zsh> ./cnf/bin/afnix-setup -o --prefix=/usr/local/afnix zsh> make status zsh> make [-j] zsh> make test zsh> make install zsh> make clean

With some platforms, the `make` should be replaced by the `gmake`. The `make status` is optional and can be used to report the internal value contents. In particular, the version and the installation parameters are reported.

## Configuration

The `afnix-setup` command can be invoked to setup a particular configuration. You should have your compiler on your search path. Normally, the command given below is enough.

zsh> ./cnf/bin/afnix-setup -o --prefix=/usr/local/afnix

This command checks that the target platform can be detected and configured. The `-o` option configures the compilation in optimized mode. Use the `-g` option can be used to configure the build process in debug mode. The `--prefix` option sets the installation directory. Note that the compilation process is done in the distribution tree and that the `--prefix` option affects only the installation operations. The `-v` option is the verbose option. Other options are available for fine tuning.

## AFNIX setup options

Option | Description | Default
-h | Print a help message | n/a
-v | Set the verbose mode | n/a
-g | Set the debug mode | yes
-o | Set the optimized mode | no
--help | Same as -h | n/a
--prefix | Set the target installation directory | /usr/local
--shrdir | Set the shared installation directory | /usr/local/share
--altdir | Set the alternate installation directory | /usr/local
--sdkdir | Set the system development kit directory | platform dependent
--compiler | Set the default compiler | platform dependent
--proctype | Set the processor type for fine tuning | generic
--dynamic | Compile and link dynamically | yes
--static | Compile and link statically | no

the `prefix` option set the root installation directory. The binary and library installation directories are derived from it. The `shrdir` set the shared installation directory which is normally used for the installation of the manual pages on most popular systems. the `altdir` sets the alternate installation directory. Normally this path should be empty as it affects the path for the etc directory. This flag should be used when using a prefix to unusual destination. the `sdkdir` option sets the path of the platform system development kit. This option is only used with the Darwin platform. The `compiler` option can be used to force a particular compiler with the help of a compiler configuration file. The `proctype` option can be used to force a particular processor architecture. The `-s` or `--static` option can be used to build a static executable. Normally, this option should not be used since it restrict the use of extension modules. The `dynamic` controls whether or not the dynamic libraries should be built. This option is detected automatically for a particular platform and should be used only by package maintainer.

## Compiling the distribution

The compilation process is straightforward. With some platforms, the `make` accepts the `-j` that enable parallelization.

zsh> make [-j]

This will build the complete distribution locally. If an error occurs, it is best to report it at the AFNIX bug report mail address.

## Testing the distribution

The distribution contains all test suites. The test suites are compiled and executed with the following command.

zsh> make test

This command run the test suites for each library as well as the test suites for each application client. Most of the base library test suites are written in C++ while the application test suites are written in .

## Installing the distribution

Once the system has been built and tested, it can be installed. By default, the distribution tree is installed into the /usr/local directory. This can be overwritten with the `--prefix` option during the configuration process.

zsh> make install

There are several variables that controls the behavior of the `install` rule. Each variable has its default value sets during the setup configuration. However, this variable can also be altered during the installation process

## AFNIX install rule variables

Variable | Description | Default
PREFIX | The root installation directory | /usr/local
SHRDIR | The shared installation directory | /usr/local/share
ALTDIR | The shared alternate directory | /usr/local/etc
SDKDIR | The system development kit directory | platform dependent
BINDIR | The binary executable installation directory | prefix/bin
LIBDIR | The library installation directory | prefix/lib
HDRDIR | The development header files installation directory | prefix/include/afnix
DOCDIR | The documentation installation directory | shrdir/doc/afnix
MANDIR | The manual pages installation directory | shrdir/man
ETCDIR | The extra files installation directory | altdir/etc/afnix

## Cleaning the distribution

The distribution is cleaned with the `clean` rule.

zsh> make clean

This rule does not clean the configuration. For a complete cleaning the `distclean` rule is more appropriate.

zsh> make distclean

## Running AFNIX

The `afnix` command invokes the interpreter. In order to operate properly, the LD_LIBRARY_PATH environment variable must be configured with the directory containing the shared libraries. If the libraries have been installed in a standard location like /usr/local/lib, there is nothing to do.

## Running some example

The directory exp contains various examples which can be run. Each example is labeled according to their use in the volume 1 of the documentation set. Example 0101.als prints the message `hello world`. Example 0501.als prints various information about the system configuration.

zsh> axi 0501 major version number : minor version number : patch version number : interpreter version : .. operating system name : linux operating system type : unix afnix official url : http://www.afnix.org

## Special features

The build process provides several features that permits to customize the compilation process as well as the nature of the final executable. Most of the time, these options are reserved for the package maintainer and are given below for illustration purpose.

## Target customization

The distribution can be configured to operate on a specific machine target. For example, a typical Linux box will be compiled with the default compiler target, which is the 386 processor. You can force the compilation to be optimized for a particular processor. This is done with the `--proctype` option of the `afnix-setup` command. Currently the distribution supports the `586` and `686` architectures for the Intel platform. The `ultra` architecture is valid for the SPARC platform.

zsh> cnf/bin/afnix-setup -o --prefix=/usr/local --proctype=586

This command will configure the distribution to be compiled specifically for the Pentium architecture.

## Special target extensions

Extensions are specific libraries or executables which are not build automatically during the build process. The user is responsible to decide which extension is needed for the system All extensions are located under the src/ext directory. Simply going into the appropriate directory and running the `make` command will build the extension.

The asi extension creates a static interpreter with all libraries automatically included in the final executable. The extension is simply build with the following command. Note that this extension overwrite the previous executable in the bld/bin directory.

zsh> make -C src/ext/asi

## Extra files

comes with some extra files. The most important is the afnix-mode for Emacs. The original source file is written in Emacs Lisp and is available in the etc directory of the distribution. This file should be installed according to the current Emacs installation.