| 1 |
Compilation |
| 2 |
==================== |
| 3 |
|
| 4 |
The Python bindings do not require compilation. |
| 5 |
|
| 6 |
Pre-Requisites |
| 7 |
==================== |
| 8 |
|
| 9 |
The Python bindings make use of the ctypes library. ctypes is included as part |
| 10 |
of Python 2.5. It is also available as an optional module for older versions |
| 11 |
of Python. See the following URL for pointers: |
| 12 |
|
| 13 |
http://sourceforge.net/projects/ctypes/ |
| 14 |
|
| 15 |
Installation |
| 16 |
==================== |
| 17 |
|
| 18 |
The Python bindings make use of distutils for installation purposes. distutils |
| 19 |
is a standard part of Python. Simply run the following command: |
| 20 |
|
| 21 |
python setup.py install |
| 22 |
|
| 23 |
You will probably need to run this command as root, since installation |
| 24 |
requires writing files to system directories. |
| 25 |
|
| 26 |
Direct Usage |
| 27 |
==================== |
| 28 |
|
| 29 |
Since the Python bindings do not require compilation, they may be used |
| 30 |
directly without installation. To do this, simply add the directory containing |
| 31 |
the bindings to your PYTHONPATH. For example: |
| 32 |
|
| 33 |
export PYTHONPATH=/path/to/libconcord/bindings/python |
| 34 |
|
| 35 |
Debugging |
| 36 |
==================== |
| 37 |
|
| 38 |
If you set the environment variable LIBCONCORD_PY_TRACE to string "1", then |
| 39 |
libconcord.py will trace all function calls. This may prove helpful when |
| 40 |
debugging client applications. |
| 41 |
|
| 42 |
For example, in bash: |
| 43 |
|
| 44 |
LIBCONCORD_PY_TRACE=1 ./congruity /path/to/Connectivity.EZHex |
| 45 |
|