SWIG image
Home Development Mailing Lists Bugs and Patches
Information
What is SWIG?
Compatibility
Features
Tutorial
Documentation
News
The Bleeding Edge
History
Subversion
Guilty Parties
Projects
Legal Department
Links
Download
SwigWiki
Exits
AllegroCL
C# - Mono
C# - MS .NET
CFFI
CHICKEN
CLISP
Guile
Java
Lua
MzScheme
Ocaml
Octave
Perl
PHP
Python
R
Ruby
Tcl/Tk
Our Generous Host
SourceForge logo

SVN

Development versions of SWIG are available through the SVN server located at SourceForge.

Disclaimer

The SVN release represents work in progress and is not guaranteed to compile on your machine or be functional in any manner.

Required Tools

To compile SWIG from its SVN repository, you will need the following tools:
  • Autoconf 2.58 or higher
  • Automake 1.7.2 or higher
  • A working C++ compiler.
  • yacc or bison (to compile the SWIG parser).

It is important to note that the SVN repository does not include the C++ code generated by yacc nor the files produced by Autoconf or Automake (these are however included in a normal release). Thus, you will have to install these tools on your machine for everything to work.

To check out the latest version

There are generic SVN instructions available on the SourceForge site, but the steps below should be all you need. The instructions below are for those who have read only access for SVN, developers should consult the generic SVN instructions above.

  1. The latest development version of SWIG can be retrieved using 

     % svn co https://swig.svn.sourceforge.net/svnroot/swig/trunk swig

  2. To build the system, follow these steps 

     % cd swig
 % ./autogen.sh
 % ./configure --prefix=/some/directory
 % make
 % make install

  3. To check the build, run the tests: 

     % make -k check
    This could take up to an hour or longer. If you are interested in a particular language, just check the examples and test-suite for that language. For example, the Python tests: 
     % make check-python-examples
 % make check-python-test-suite
Note: The SVN repository is read-only so the system will not accept code modifications unless you are registered as a developer by the SWIG project.

Build Issues

Here are some guidelines should you be experiencing problems building SWIG from SVN.
  1. Check that you have a complete update from the SWIG SVN repository. A fresh checkout from SVN often solves build problems.
  2. Make sure you have run ./autogen.sh and ./configure. Both these steps will be necessary if you have a fresh SVN checkout or if the build files in the repository have changed since a previous update.
  3. Check that the appropriate versions of your autotools (Autoconf and Automake) are installed properly. The autotools are in a state of flux and there are backward compatibility issues which are solved in different ways on different operating systems.
  4. Check that all the autotool bootstrap programs which are executed when running ./autogen.sh are up to date and match your installed autotool versions. For example aclocal --version should report a matching version of Automake or Autoconf, something like "aclocal (GNU automake) 1.7.6".
If you are still having problems, send an email to swig-devel mailing list.

Developer Access

We are always looking for people to help out with various projects.

  • Send email to to the swig-devel mailing list. if you are interested in doing developer work and gaining write access to the SVN repository.

  • The swig-devel mailing list is the developer mailing list and should be used to discuss coding issues, bugs, patches, and so forth. Subscription information and archives of recent activity can be found on the mailing lists page.

Feedback and questions concerning this site should be posted to the swig-devel mailing list.

Last modified : Thu Sep 27 21:25:52 2007