swig/Examples
Gonzalo Garramuno 5be075f16f Added some runtime tests for ruby.
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@9693 626c5289-ae23-0410-ae9c-e8d60b6d4f22
2007-04-28 15:52:50 +00:00
..
chicken Remove cvsignore files: this is stored on svn:igonre property now 2006-12-03 08:28:42 +00:00
contract fix extern declarations 2005-06-28 21:14:24 +00:00
csharp add missing c# tests 2007-04-18 09:47:01 +00:00
GIFPlot Remove cvsignore files: this is stored on svn:igonre property now 2006-12-03 08:28:42 +00:00
guile Remove cvsignore files: this is stored on svn:igonre property now 2006-12-03 08:28:42 +00:00
java Remove cvsignore files: this is stored on svn:igonre property now 2006-12-03 08:28:42 +00:00
lua Added a lua specific carrays.i which adds the operator[] support. 2007-01-22 04:59:16 +00:00
modula3 Remove cvsignore files: this is stored on svn:igonre property now 2006-12-03 08:28:42 +00:00
mzscheme Remove cvsignore files: this is stored on svn:igonre property now 2006-12-03 08:28:42 +00:00
ocaml force examples to use preinst-swig, as is done in the test-suite 2005-11-27 02:17:20 +00:00
perl5 Remove cvsignore files: this is stored on svn:igonre property now 2006-12-03 08:28:42 +00:00
php4 Remove cvsignore files: this is stored on svn:igonre property now 2006-12-03 08:28:42 +00:00
pike Remove cvsignore files: this is stored on svn:igonre property now 2006-12-03 08:28:42 +00:00
python [Python] Fix lack of generation of docstrings when -O is used. 2007-04-20 01:16:31 +00:00
r Committing R-SWIG 2006-06-29 03:01:18 +00:00
ruby Remove cvsignore files: this is stored on svn:igonre property now 2006-12-03 08:28:42 +00:00
s-exp Minor fix to the example. 2004-10-30 17:58:16 +00:00
tcl Remove cvsignore files: this is stored on svn:igonre property now 2006-12-03 08:28:42 +00:00
test-suite Added some runtime tests for ruby. 2007-04-28 15:52:50 +00:00
xml Remove cvsignore files: this is stored on svn:igonre property now 2006-12-03 08:28:42 +00:00
index.html The great merge 2002-11-30 22:01:28 +00:00
Makefile.in On windows use .pyd instead of .dll - Python-2.5 no longer works with dlls 2006-11-20 21:34:27 +00:00
README Added chicken to list of example directories. 2003-02-15 01:58:36 +00:00

SWIG Examples

The "perl5", "python", "tcl", "guile", "java", "mzscheme", "ruby", and
"chicken" directories contain a number of simple examples that are
primarily used for testing. The "GIFPlot" directory contains a more
complicated example that illustrates some of SWIG's more advanced
capabilities.

The file 'index.html' is the top of a hyperlinked document that
contains information about all of the examples along with various
notes related to each example.

The Examples directory is currently quite incomplete because it
is being reorganized.  A more complete set of examples can be found
in the SWIG1.1p5 distribution (most of which should still work with
SWIG1.3).

Note: All of the examples rely upon the Makefile in this directory.
You may need to edit it to reflect the configuration of your machine
in case the configure script guesses incorrect settings.


*** Special note concering C++ ***

The configure script is currently unable to handle all of the possible
options for producing dynamically loadable C++ extensions.  Here are
the rules of thumb for making C++ work:

 -  Try using the C++ as the linker for the shared library.  For example:

         g++ -shared $(OBJS) -o module.so

 -  If that doesn't work, you may need to explicitly link against some
    kind of C++ runtime library.  For example:

         ld -G $(OBJS) -L/opt/SUNWspro/lib -lCrun -o module.so

    This can be set by modifying the setting of CPP_DLLIBS in the
    Makefile.


*** Special note for SWIG Maintainers ***

When you add an example, consider arranging for the example to be also
useful as part of the SWIG testing framework.  To do this, include in
the example makefile a target "check" ("check: all" is sufficient for a
first pass), and add an invocation to ../Makefile.in under target
"check-examples" (or whatever is appropriate).  Later, we can add or
expand the actions under target "check" to do more in-depth testing.