Binaries:

    Just make sure, that your enviroment variables are set as it said in HOWTOPLAY file and
    themes directory (or symbolic link to it) is set to the current directory, from you want to start Attal

Sources:

We are now using qmake for building Attal.

For using qmake you must be sure that the environment variables QMAKESPEC and QTDIR are correctly sets.
For more information, read the documentation given with qt about qmake.

Note that you will need to have (at least) qt 4.0.1 installed (lib and include files).
Attal is tested with various gcc compilers, from gcc 3.2.2 to gcc 4
Note that for compile themes directory need to be placed in src2 directory

If you have some problems to find libraries set the environment variable LD_LIBRARY_PATH to local directory like this:
export LD_LIBRARY_PATH=.

Now, do the following steps:
$ qmake -o Makefile Makefile.pro
$ make
$ make install (as root)

Or, better under unix , do the following steps:
$ ./autogen.sh
$ make
$ make install (as root)
$ /sbin/ldconfig (as root)

Well, everything should be ok now.
You can launch :
- the client:
	$ attal-client &
- the server:
	$ attal-server &
- the ia-client:
	$ attal-ai &
- the scenario editor:
	$ attal-scenario-editor &
- the theme editor:
	$ attal-theme-editor &
- the campaign editor:
	$ attal-campaign-editor &

IMPORTANT NOTE: all the executables need to find the theme (medieval theme for the moment) and so the folder 'themes',
which have to contain the 'medieval' theme, must be present in the current directory (where there are the binaries). 
(only if you play in local directory, with make install it is not necessary)

NOTE: to uninstall the game use:
$ make uninstall (as root)

You can edit config.pro for setting some global options (for example compiling in static if you got problem with dynamic libs).

If you have some problems for compiling it, you can read INSTALL.Debian
which relates a user experience for compiling it on Debian...

If you have some problems for compiling it on MacosX, that seem not manage well dynamic libs
try to compile with staticlib, uncommenting 

	#CONFIG += staticlib

in config.pro

If you want to debug some part of code, please try to compile with debug option, uncommenting

 #CONFIG += debug

as above

Sound in compilation from source code is enabled , if you want to disable this, commenting like this

 #DEFINES += WITH_SOUND

For different options of compilation, read comments in config.pro


If you want to choose a different installation directory all you have to do is:

 export ATT_PREFIX=your path

before autogen.sh

If you want to choose an installation directory different from final directory where you will place themes you have to do is:

 export ATT_DATA_PREFIX=your path

before autogen.sh

If you have two or more QT installation you have to export the path to libraries you use like this:

 export QTDIR=path to qt
