swig/Examples
William S Fulton 9e4bce051d Merge branch 'wkalinin-csymbols-1'
* wkalinin-csymbols-1:
  obscure case workaround in std::set wrapper, where ignored type still need to be processed
  global unnamed structures ignored
  test added for nested unnamed C struct %extend
  %extend for nested unnamed C structs
2014-05-20 18:10:41 +01:00
..
android Fix out of source clean-android-examples 2014-05-15 23:28:47 +01:00
chicken Add in CPPFLAGS and LDFLAGS to examples/test-suite 2014-05-15 23:11:08 +01:00
contract fix extern declarations 2005-06-28 21:14:24 +00:00
csharp Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
d Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
go Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
guile Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
java Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
javascript Javascript examples tidy up 2014-05-18 00:59:47 +01:00
lua Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
modula3 Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
mzscheme Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
ocaml Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
octave Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
perl5 Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
php Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
pike Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
python Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
r Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
ruby Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
s-exp remove final vestiges of gifplot example 2010-02-28 00:16:39 +00:00
tcl Allow examples and test-suite to be built out of source tree 2014-05-11 23:21:10 +02:00
test-suite Merge branch 'wkalinin-csymbols-1' 2014-05-20 18:10:41 +01:00
xml XML example makefiles tweaks for consistency with other languages 2013-04-19 22:47:29 +01:00
index.html remove final vestiges of gifplot example 2010-02-28 00:16:39 +00:00
Makefile.in Javascript examples tidy up 2014-05-18 00:59:47 +01:00
README Improve Examples/README 2014-02-21 08:14:24 +13:00

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.