1Building Perl or Python (through swig) 2------------- 3 4Using autotools 5--------------- 6See swig/packages/README 7 8Using CMake 9----------- 10Building the SWIG (Perl, Python) bindings with the CMake toolchain requires installing 11the CMake application appropriate to your operating system (most Linux distributions 12will have this as an existing package as CMake is integral to building many popular 13applications). 14 15Additionally you will need the development packages for the language you are targeting 16and the swig application itself. All of these should be directly available through your 17distribution's package system. 18 19Python: In Fedora you can get this with a 'yum install python-devel' and a similar call 20to apt-get in Debian/Ubuntu/etc. 21Perl: In Fedora you're looking for 'yum install perl-devel' and the equivalent package 22in Debian/Ubuntu/etc. 23 24After this, you need to add the argument -DSWORD_BINDINGS="Python" or 25-DSWORD_BINDINGS="Perl" when you invoke CMake. If you wish to build both bindings then 26just call -DSWORD_BINDINGS="Python Perl" instead. This needs to be done at the level of 27the whole SWORD library and not just here within the bindings directory. The files will 28be installed to their standard system-wide location when you run 'make install' with 29the rest of the library. 30 31If you wish to install the Python bindings to another directory instead you can specify 32the option -DSWORD_PYTHON_INSTALL_DIR="/some/other/path" at configure time. No comparable 33option is currently available for the Perl bindings because the maintainer is unaware 34of how to implement it. 35 36Building java 37------------- 38 39The source can be built with sun java (javac) or with GNU Classpath (jikes-classpath) 40GJC does not yet work, corba is expected to work with gcj 4.1 41 42set the JAVAC environment variable to whichever you wish to build with 43 44e.g. JAVAC=javac ./configure 45