swig/Examples
Vadim Zeitlin 6c5d00bd0d Ignore ambiguous variable names error from pycodestyle 2.6
This error is given for any use of variable called "l" (and also "I" and
"O", but we don't seem to have any of those) and it doesn't seem to be
worth changing this variable name in the tests code, as it's really not
that meaningful there anyhow, so just disable the warning to let the CI
builds, which now use pycodestyle 2.6, instead of 2.5 which didn't have
this error and which is still the latest available in Debian Sid, pass.
2020-05-22 16:17:45 +02:00
..
android
chicken
contract
csharp
d
go Fix all Go tests to build with "go build" 2019-08-08 14:30:50 -07:00
guile Remove use of std::bind2nd which is removed in C++17 2019-06-27 07:40:49 +01:00
java Java 9 deprecation warning fixes for test-suite and examples 2019-02-21 13:47:39 -08:00
javascript Dev Checkpoint 201906261312 2019-06-26 13:12:19 -06:00
lua Misc. typos 2018-05-17 10:04:23 -04:00
modula3
mzscheme Remove use of std::bind2nd which is removed in C++17 2019-06-27 07:40:49 +01:00
ocaml Remove use of std::bind2nd which is removed in C++17 2019-06-27 07:40:49 +01:00
octave Misc. typos 2018-05-17 10:04:23 -04:00
perl5 Misc. typos 2018-05-17 10:04:23 -04:00
php Fix php pragmas example include path 2019-05-09 07:35:24 +01:00
pike
python Examples: Unify string quoting in the Python sources 2019-07-14 14:12:23 +10:00
r
ruby Remove use of std::bind2nd which is removed in C++17 2019-06-27 07:40:49 +01:00
s-exp
scilab Remove use of std::bind2nd which is removed in C++17 2019-06-27 07:40:49 +01:00
tcl Remove use of std::bind2nd which is removed in C++17 2019-06-27 07:40:49 +01:00
test-suite Ignore ambiguous variable names error from pycodestyle 2.6 2020-05-22 16:17:45 +02:00
xml
index.html
Makefile.in Fix Go version check and Go in-tree example tests 2019-08-09 14:06:45 -07: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.