Updated README and minor buld tweaks for OS X (That will probably break the Linux build (sigh)).

1 files changed, 48 insertions, 0 deletions

diff --git a/README b/README
index cfbba22..5c71263 100644
--- a/README
+++ b/README
@@ -36,6 +36,54 @@ There following configure flags are optional:
 --enable-fft (to enable functions that require fftw3)
 --enable-simpletest (to build the simpletest example)
 
+Building the Python bindings
+----------------------------
+
+To build the python bindings, add to your configure flags:
+
+--enable-swig --with-python
+
+This requres additional dependencies to be resolved:
+
+swig >= 1.3
+python (with development files) >= 2.5
+
+It might work with earlier versions of Python, but this has not been tested.
+
+If you do not have the 'standard' version of Python on OS X, you might need to tell the configure script where the python library is e.g.:
+
+./configure --your-flags LDFLAGS="-L/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config/"
+
+to find your Python library type:
+
+locate libpython
+
+Building the Java bindings
+--------------------------
+
+To build the java bindings, add to your configure flags:
+
+--enable-swig --with-java
+
+This requres additional dependencies to be resolved:
+
+swig >= 1.3
+java (with development files) >= 2.0
+
+It might work with other versions of Java, but this has not been tested.
+
+On OS X, you will probably need to set your CLASSPATH environment variable before running ./configure
+
+export CLASSPATH=/System/Library/Frameworks/JavaVM.framework/Classes/classes.jar
+
+On OS X, you also probably need to tell the configure script where to find your Java (JNI) headers.
+
+./configure --flags  CFLAGS="-I/System/Library/Frameworks/JavaVM.framework/Headers"
+
+To find out where your headers are:
+
+locate jni.h
+
 Disclaimer
 ----------