swig/Examples
Olly Betts f66a81fcb4 Fix extension of filename in comments in examples 2024-09-16 16:51:44 +12:00
..
android
c Fix extension of filename in comments in examples 2024-09-16 16:51:44 +12:00
csharp
d Tidy up EXTRA_ build flags 2024-03-24 18:12:21 +00:00
go Update examples to recommend compiling with -fPIC instead of -fpic 2024-07-22 17:46:29 -04:00
guile Remove redundant NULL checks before free()/delete (#2184) 2022-01-29 22:03:48 +13:00
java [java] Avoid using deprecated API in doxygen example 2024-03-01 10:41:01 +13:00
javascript Fix extension of filename in comments in examples 2024-09-16 16:51:44 +12:00
lua Fix extension of filename in comments in examples 2024-09-16 16:51:44 +12:00
mzscheme Remove use of std::bind2nd which is removed in C++17 2019-06-27 07:40:49 +01:00
ocaml [ocaml] Avoid non-unit-statement warnings in examples 2024-02-24 08:27:48 +13:00
octave Fix extension of filename in comments in examples 2024-09-16 16:51:44 +12:00
perl5 Update examples to recommend compiling with -fPIC instead of -fpic 2024-07-22 17:46:29 -04:00
php Fix extension of filename in comments in examples 2024-09-16 16:51:44 +12:00
python Fix extension of filename in comments in examples 2024-09-16 16:51:44 +12:00
r
ruby Fix extension of filename in comments in examples 2024-09-16 16:51:44 +12:00
scilab Fix extension of filename in comments in examples 2024-09-16 16:51:44 +12:00
tcl Fix extension of filename in comments in examples 2024-09-16 16:51:44 +12:00
test-suite Straighten out handling of integer constants 2024-09-16 16:10:02 +12:00
Makefile.in Merge branch 'master' into C 2024-09-13 12:31:14 +12:00
README
index.html

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.