swig/Examples
Vadim Zeitlin f42b0eaa71 Use different executable names for C and C++ examples
Trying to create the same "runme" executable for both C and C++ examples
could result in errors when using parallel make, as one of the targets
could fail to write to the file being currently executed.

Using separate names works around this problem.
2021-11-27 00:19:05 +01:00
..
android
c Don't use exception specification with C++ compiler in example 2021-11-24 20:16:42 +01:00
csharp
d
go Fix all Go tests to build with "go build" 2019-08-08 14:30:50 -07:00
guile Alphabetise testing of examples 2020-08-13 20:07:10 +01:00
java Java 9 deprecation warning fixes for test-suite and examples 2019-02-21 13:47:39 -08:00
javascript Convert javascript_arrays.i example into testcase 2021-03-06 10:55:47 +00:00
lua Lua example fix for newer osx 2021-02-20 14:47:03 +00:00
mzscheme Remove use of std::bind2nd which is removed in C++17 2019-06-27 07:40:49 +01:00
ocaml [S-EXP] Remove code for Common Lisp S-Exp 2021-05-16 08:42:39 +12:00
octave Alphabetise testing of examples 2020-08-13 20:07:10 +01:00
perl5
php Fix and restore disabled code in PHP value example 2021-05-04 14:21:13 +12:00
python Revert accidental change to Python example 2021-11-04 01:31:06 +01:00
r
ruby Remove use of std::bind2nd which is removed in C++17 2019-06-27 07:40:49 +01:00
scilab Alphabetise testing of examples 2020-08-13 20:07:10 +01:00
tcl Remove use of std::bind2nd which is removed in C++17 2019-06-27 07:40:49 +01:00
test-suite Enable testing some C++ wrappers code in the test suite 2021-11-24 02:41:33 +01:00
xml
index.html
Makefile.in Use different executable names for C and C++ examples 2021-11-27 00:19:05 +01:00
README

SWIG Examples

The subdirectories of "Examples" named after SWIG's language backends
contain a number of simple examples that are primarily used for testing.

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.

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 concerning 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.