PageRenderTime 41ms CodeModel.GetById 14ms RepoModel.GetById 0ms app.codeStats 0ms

/trunk/Examples/README

#
#! | 47 lines | 32 code | 15 blank | 0 comment | 0 complexity | 580af468bab50416d49f4d9f253ad892 MD5 | raw file
Possible License(s): LGPL-2.1, Cube, GPL-3.0, 0BSD, GPL-2.0
  1. SWIG Examples
  2. The "perl5", "python", "tcl", "guile", "java", "mzscheme", "ruby", and
  3. "chicken" directories contain a number of simple examples that are
  4. primarily used for testing.
  5. The file 'index.html' is the top of a hyperlinked document that
  6. contains information about all of the examples along with various
  7. notes related to each example.
  8. The Examples directory is currently quite incomplete because it
  9. is being reorganized. A more complete set of examples can be found
  10. in the SWIG1.1p5 distribution (most of which should still work with
  11. SWIG1.3).
  12. Note: All of the examples rely upon the Makefile in this directory.
  13. You may need to edit it to reflect the configuration of your machine
  14. in case the configure script guesses incorrect settings.
  15. *** Special note concering C++ ***
  16. The configure script is currently unable to handle all of the possible
  17. options for producing dynamically loadable C++ extensions. Here are
  18. the rules of thumb for making C++ work:
  19. - Try using the C++ as the linker for the shared library. For example:
  20. g++ -shared $(OBJS) -o module.so
  21. - If that doesn't work, you may need to explicitly link against some
  22. kind of C++ runtime library. For example:
  23. ld -G $(OBJS) -L/opt/SUNWspro/lib -lCrun -o module.so
  24. This can be set by modifying the setting of CPP_DLLIBS in the
  25. Makefile.
  26. *** Special note for SWIG Maintainers ***
  27. When you add an example, consider arranging for the example to be also
  28. useful as part of the SWIG testing framework. To do this, include in
  29. the example makefile a target "check" ("check: all" is sufficient for a
  30. first pass), and add an invocation to ../Makefile.in under target
  31. "check-examples" (or whatever is appropriate). Later, we can add or
  32. expand the actions under target "check" to do more in-depth testing.