swig/Examples
William S Fulton 7f40ae3570 C# project files update
- Update project files to use Visual Studio 2005 (minimum supported .NET
  is now 2.0 which is what VS 2005 supports).
- Add project files for arrays example (requires /unsafe)
- Fix support so that the project files work straight out the box on 64
  bit systems (32 bit compile is the default).
- Fix support for 64 bit builds - use the x64 platform.
2014-02-23 15:47:42 +00:00
..
android Fix typos 2013-09-25 17:29:33 +12:00
chicken Chicken - make check-examples run like other examples - not all run very well though! 2013-04-20 02:28:48 +01:00
contract fix extern declarations 2005-06-28 21:14:24 +00:00
csharp C# project files update 2014-02-23 15:47:42 +00:00
d Fix gcc -Waddress warning in variables examples 2013-10-18 06:53:02 +01:00
go Fix assorted comment and documentation typos 2014-02-23 17:15:22 +13:00
guile Add missing executable bit 2014-02-22 21:24:55 +00:00
java Improve the class example for several languages. 2014-02-23 18:24:51 +13:00
lua Fix assorted comment and documentation typos 2014-02-23 17:15:22 +13:00
modula3 Modula3 makefiles tweaks for consistency with other languages - they still don't work though 2013-04-19 22:47:28 +01:00
mzscheme Mzscheme - fix for running examples during 'make check-examples' - they don't run very well though\! 2013-04-20 02:28:48 +01:00
ocaml Ocaml example makefiles tweaks for consistency with other languages. Attempt to add runtime tests to 'make check' - untested. 2013-04-19 22:47:28 +01:00
octave Fix gcc -Waddress warning in variables examples 2013-10-18 06:53:02 +01:00
perl5 Improve the class example for several languages. 2014-02-23 18:24:51 +13:00
php Improve the class example for several languages. 2014-02-23 18:24:51 +13:00
pike Remove executable bit from various test-suite runme files 2014-01-06 15:41:06 +13:00
python Improve the class example for several languages. 2014-02-23 18:24:51 +13:00
r R examples makefile tidyup 2013-04-19 22:47:26 +01:00
ruby Improve the class example for several languages. 2014-02-23 18:24:51 +13:00
s-exp remove final vestiges of gifplot example 2010-02-28 00:16:39 +00:00
tcl Improve the class example for several languages. 2014-02-23 18:24:51 +13:00
test-suite Fix assorted comment and documentation typos 2014-02-23 17:15:22 +13: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 Fix assorted comment and documentation typos 2014-02-23 17:15:22 +13: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.