Next: 2.2 On a Windows Up: 2. Installing Fnorb Previous: 2. Installing Fnorb

# 2.1 On a Unix System

To use the IDL compiler `fnidl` you must have a C/C++ pre-processor installed on your path. By default, Fnorb looks for one with the name `gcc`, or `cpp`, but if you have some other pre-processor then you must edit the file ```Fnorb/script/cpp.py`'' and set the `COMMAND` variable as appropriate.

1.
  Unpack the Fnorb distribution (the recommended place to put it is in your Python ```site-packages`'' directory).

  `$ gunzip fnorb-1.1.tar.gz`
  `$ tar xvf fnorb-1.1.tar`

2.
  Make a symbolic link ```Fnorb`'' to point to the directory created by the unpack.

  `$ ln -s Fnorb-1.1 Fnorb`

3.
  Build the extension modules.

      $ cd Fnorb/src
      $ make -f Makefile.pre.in boot
      $ make

4.
  Copy the built extension modules into a location on your Python path. If you have a single architecture you can simply put the extension modules in the directory that you installed Fnorb in:

      $ cp *.so /Where/You/Put/Fnorb

  If your installation shares a filesystem across multiple architectures a good place to put them would be in the platform specific directory of your Python library:

      $ cp *.so .../python-1.5/lib/plat-sunos5

5.
  Set the following environment variables: For Bourne like shells:

      INSTALL_DIR=/Where/You/Put/Fnorb
      export PATH=$PATH:$INSTALL_DIR/Fnorb/script
      export PYTHONPATH=$PYTHONPATH:$INSTALL_DIR

  Or for csh like shells:

      set INSTALL_DIR=/Where/You/Put/Fnorb
      setenv PATH {$PATH}:{$INSTALL_DIR}/Fnorb/script
      setenv PYTHONPATH {$PYTHONPATH}:{$INSTALL_DIR}

  You probably want to set these in your shell's initialisation scripts.

Next: 2.2 On a Windows Up: 2. Installing Fnorb Previous: 2. Installing Fnorb