| 1 |
How to compile AisleRiot on different platforms |
| 2 |
=============================================== |
| 3 |
|
| 4 |
The AilseRiot code supports different platforms: GNOME (using GConf), and |
| 5 |
GTK only. |
| 6 |
|
| 7 |
To compile it for some platform, configure with |
| 8 |
|
| 9 |
./configure --with-platform=gnome |
| 10 |
or |
| 11 |
./configure --with-platform=gtk-only |
| 12 |
|
| 13 |
Environment variables |
| 14 |
===================== |
| 15 |
|
| 16 |
You can set the following environment variables to influence the |
| 17 |
behaviour of AisleRiot: |
| 18 |
|
| 19 |
AR_DEBUG: |
| 20 |
Values: all | help | ... |
| 21 |
|
| 22 |
Use AR_DEBUG=help to get a list of supported debuggin options. |
| 23 |
|
| 24 |
AR_CARD_THEME_PATH_{SVG,KDE,SLICED,FIXED,PYSOL}: |
| 25 |
Values: a colon-separated list of paths |
| 26 |
Default: empty |
| 27 |
|
| 28 |
Set these variables to add extra paths to check for card themes. |
| 29 |
|
| 30 |
Debugging & Valgrinding AisleRiot |
| 31 |
================================= |
| 32 |
|
| 33 |
If you configure with --enable-debug, there is extra debugging |
| 34 |
output available by setting the GAMES_DEBUG env variable. Use |
| 35 |
GAMES_DEBUG=help to see the list of available debug flags. |
| 36 |
|
| 37 |
When using valgrind, use the included ../data/aisleriot.supp suppressions file to |
| 38 |
suppress common valgrind errors relating to guile's garbage collection. |
| 39 |
|
| 40 |
There are also some debugging options available in the UI if you |
| 41 |
configure with --enable-debug-ui . |
| 42 |
|
| 43 |
How to write a new game for Aisleriot |
| 44 |
===================================== |
| 45 |
|
| 46 |
See ../games/README. |