|Original author(s)||Dave Beazley|
|Initial release||February 1996|
|Stable release||3.0.7 / August 3, 2015|
|Written in||C, C++|
The aim is to allow the calling of native functions (that were written in C or C++) by other programming languages, passing complex data types to those functions, keeping memory from being inappropriately freed, inheriting object classes across languages, etc. The programmer writes an interface file containing a list of C/C++ functions to be made visible to an interpreter. SWIG will compile the interface file and generate regular C/C++ as well as code in the target programming language. SWIG will generate conversion code for functions with simple arguments; conversion code for complex types of arguments must be written by the programmer. The SWIG tool creates source code that provides the glue between C/C++ and the target language. Depending on the language, this glue comes in two forms:
- a shared library that an extant interpreter can link to as some form of extension module, or
- a shared library that can be linked to other programs compiled in the target language (for example, using JNI in Java).
SWIG is not used for calling interpreted functions by native code; this must be done by the programmer manually.
There are two main reasons to embed a scripting engine in an existing C/C++ program:
- The program can then be customized far faster, via a scripting language instead of C/C++. The scripting engine may even be exposed to the end user, so that they can automate common tasks by writing scripts.
- Even if the final product is not to contain the scripting engine, it may nevertheless be very useful for writing test scripts.
There are several reasons to create dynamic libraries that can be loaded into extant interpreters, including:
- Provide access to a C/C++ library which has no equivalent in the scripting language.
- Write the whole program in the scripting language first, and after profiling, rewrite performance critical code in C or C++.
SWIG is written in C and C++ and has been publicly available since February 1996. The initial author and main developer was Dave Beazley who developed SWIG while working as a graduate student at Los Alamos National Laboratory and the University of Utah and while on the faculty at the University of Chicago. Development is currently supported by an active group of volunteers led by William Fulton. SWIG has been released under a GNU General Public License.
Google Summer of Code
SWIG was a successful participant of Google Summer of Code in 2008, 2009, 2012. In 2008, SWIG got four slots. Haoyu Bai spent his summers on SWIG's Python 3.0 Backend, Jan Jezabek worked on Support for generating COM wrappers, Cheryl Foil spent her time on Comment 'Translator' for SWIG, and Maciej Drwal worked on a C backend. In 2009, SWIG again participated in Google Summer of Code. This time four students participated. Baozeng Ding worked on a Scilab module. Matevz Jekovec spent time on C++0x features. Ashish Sharma spent his summer on an Objective-C module, Miklos Vajna spent his time on PHP directors.
Projects Using SWIG
- Language binding
- Foreign function interface
- Calling convention
- Name mangling
- Application programming interface
- Application binary interface
- Comparison of application virtual machines
- Wrapper function
- GIWS for the opposite of SWIG: calling Java from C/C++
- Article "Expose Your C/C++ Program's Internal API with a Quick SWIG" by Victor Volkman
- Article "Python Extensions In C++ Using SWIG" by Michael Fötsch
- Presentation "Application overview for openSUSE" by Klaus Kämpf