SWIG CVS

CVS

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

Disclaimer

The CVS 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 CVS 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 CVS 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 CVS 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 cvs, developers should consult the generic CVS instructions above.

Set the location of CVSROOT, for csh this would be:

 % setenv CVSROOT :pserver:anonymous@swig.cvs.sourceforge.net:/cvsroot/swig

If you are using bash, you would use:

 % export CVSROOT=:pserver:anonymous@swig.cvs.sourceforge.net:/cvsroot/swig

(Alternatively, you can use the -d option to CVS)

Log into the cvs server by issuing the following command:
```
% cvs login
CVS password: <press enter here>
```
The latest development version of SWIG can be retrieved using
```
% cvs checkout SWIG
```

To build the system, follow these steps

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

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 CVS repository is read-only so the system will not accept code modifications unless you are a developer.

Build Issues

Here are some guidelines should you be experiencing problems building SWIG from CVS.

Check that you have a complete update from the SWIG CVS repository. A fresh checkout from CVS often solves build problems.
Make sure you have run ./autogen.sh and ./configure. Both these steps will be necessary if you have a fresh CVS checkout or if the build files in the repository have changed since a previous update.
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.
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 CVS 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.