Freezer library installation

This page concerns the setup and installation of Freezer, either on a native Cell BE host, or on a cross-compilation setup.

Required tools

Freezer requires the following tools to be installed to be able to set up and build the library:

git
autoconf
automake
libtool
make
g++ for ppu
gcc for spu (spu-gcc)
eventually SDL.

Source code download

To download the latest repository version, issue the commands:

$ git clone http://github.com/fgalea/freezer.git
$ cd freezer

then, create the autotools script files:

$ ./bootstrap

Source code setup

If using on a Cell BE host, just execute the configure script:

$ ./configure

If cross compiling, you must provide a host type as argument of the configure script, either:

```
$ ./configure --host=ppu 
```
for 64-bit PPU code generation, or
```
$ ./configure --host=ppu32 
```
for 32-bit PPU code.

: If any of the previous command fails, this is certainly because one of the required tools listed above is missing.

Building the library

If the setup process went ok, you should be able to build the library using the command:

$ make

Installation of the library

The default installation directory is /usr/local. You then need the root privileges to be able to install the library. The following command will do the job:

$ make install

If you do not have the root privileges, you still can install the library to a custom directory. For this, during the setup phase you need to specify the installation directory using the --target argument to the configure script, like for instance:

$ ./configure --prefix=path/to/installation/directory

Compilation and execution of the example programs

After having compiled the library, even without installing, you can try and compile the example programs using the commands:

$ cd examples
$ make

: You should end up with a bunch of various executable files, each demo program coming in three variants, with _sdl, _ps3fb and _bmp suffixes. The SDL version is preferred when running in windowed mode, the ps3fb version is for runnnig from console mode, and the bmp version is just a test program to generate the images in bmp-formatted files, not really useful unless when debugging (or using the cell simulator when away from your ps3 for instance).