______ ___ ___ /\ _ \ /\_ \ /\_ \ \ \ \L\ \\//\ \ \//\ \ __ __ _ __ ___ \ \ __ \ \ \ \ \ \ \ /'__`\ /'_ `\/\`'__\/ __`\ \ \ \/\ \ \_\ \_ \_\ \_/\ __//\ \L\ \ \ \//\ \L\ \ \ \_\ \_\/\____\/\____\ \____\ \____ \ \_\\ \____/ \/_/\/_/\/____/\/____/\/____/\/___L\ \/_/ \/___/ /\____/ \_/__/ Unix-specific information. See readme.txt for a more general overview. Also see docs/build/linux.txt for Linux-specific information.
On Linux you have two different system drivers -- one for running using X, and one for running without X. This file describes the X version, which should be portable to any Unix variant. For information about the Linux-specific console routines, see docs/build/linux.txt.
Only the X version is installed by default.
Chances are that you already have all the necessary development tools, at least for compiling and installing the library. You will need CMake 2.6 or above. Most distributions should include it now, otherwise you will need to install it yourself.
Please follow the generic instructions in docs/build/cmake.txt.
Installing Allegro will copy the library and header files plus other support files. These are:
The options for linking with Allegro are quite complicated, since for static versions of the library, depending on how it was configured, it may need to pull in other libraries (X, SVGAlib), as well as just Allegro itself.
To avoid you having to work out the right linker commands for yourself, the installation creates a script, allegro-config, that will print out a suitable command line. You can use this inside a backtick command substitution, for example:
Or if you want to build a debug version of your program, assuming that you have installed the debug version of Allegro:gcc myfile.c -o myprogram `allegro-config --libs`
Unix newbies, take note that these are ` backticks, not normal ' quotes!gcc myfile.c -o myprogram `allegro-config --libs debug`
There are also switches for printing out the Allegro version number, overriding the install paths, and selecting between shared and static libraries, in case you installed both. Run allegro-config without any arguments for a full list of options.
You can also use pkg-config instead, for example:
As shown, there are pkg-config files for the bundled addons as well.gcc myfile.c -o myprogram `pkg-config --libs allegro loadpng`
Don't forget that you need to use the
END_OF_MAIN() macro right after
Allegro can be installed on a system where you don't have root privileges. Using the standard configure script option `--prefix' you can change the target directories for installation -- for example, you can write:
Then binaries will be installed to the `bin' subdirectory of your home directory, libraries to `lib', etc. Now you need to set up your system so that it knows where to find a few things, if this has not been done already. You might want to add these commands to your .bash_profile or similar startup script. If you use a csh-style shell, you want to use `setenv', not `export'.cmake -DCMAKE_INSTALL_PREFIX=$HOME ..
Your PATH must include the `bin' directory:
If you are using Allegro as a shared library, you need to tell the dynamic loader where to find the Allegro libraries:export PATH=$PATH:$HOME/bin
GCC needs to know where to find header and library files:export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/lib
Note: in fact `allegro-config' can handle the last step for you, if you use it for compilation as well as linking:export C_INCLUDE_PATH=$C_INCLUDE_PATH:$HOME/include export CPLUS_INCLUDE_PATH=$CPLUS_INCLUDE_PATH:$HOME/include export LIBRARY_PATH=$LIBRARY_PATH:$HOME/lib
But, it's better to set the environment variables too. Most people don't tend to bother with `allegro-config' when compiling.gcc -c mygame.c `allegro-config --cflags` gcc -o mygame mygame.o `allegro-config --libs`
Alternatively, you can get the required environment changes from allegro-config, by typing at a shell prompt:
You can catenate the output to your .bash_profile, which is pretty much like adding all of the above commands. Note that `allegro-config' itself is in the `bin' directory of the installation, so either make sure that directory is in your path before running `allegro-config' or specify the path exactly, for example:allegro-config --env
~/bin/allegro-config --env >> ~/.bash_profile
If your program requests a different color depth to the current X display, Allegro will emulate the depth you asked for, so that your program will still work, albeit more slowly than if the color depths were identical. To find out whether this emulation is taking place, look at the gfx_driver->desc field (which is displayed in the middle of the screen by the tests/test program). If this says "matching", the color formats are identical, so no conversions are required. If it says "fast", some simple conversions are taking place, but nothing too painful. If it says "slow", you are in trouble :-) This is not valid for the DGA 2.0 driver, as it'll always change the video mode to the specified resolution and color depth.
If the Irix compiler spits strange lines such as the following when compiling your Allegro program:
then you should #define ALLEGRO_NO_FIX_ALIASES prior to the #include <allegro.h> line.include/allegro/alcompat.h:59: conflicting types for `ceilf' /usr/include/math.h:311: previous declaration of `ceilf' include/allegro/alcompat.h:60: conflicting types for `floorf' /usr/include/math.h:333: previous declaration of `floorf' include/allegro/alcompat.h:63: conflicting types for `tanf' /usr/include/math.h:176: previous declaration of `tanf' include/allegro/alcompat.h:64: conflicting types for `acosf' /usr/include/math.h:106: previous declaration of `acosf' include/allegro/alcompat.h:65: conflicting types for `asinf' /usr/include/math.h:116: previous declaration of `asinf'