PageRenderTime 43ms CodeModel.GetById 15ms RepoModel.GetById 0ms app.codeStats 0ms

/trunk/Examples/python/import/README

#
#! | 39 lines | 30 code | 9 blank | 0 comment | 0 complexity | a9fce398a408f7c14a8d4fe6d13b3c3f MD5 | raw file
Possible License(s): LGPL-2.1, Cube, GPL-3.0, 0BSD, GPL-2.0
  1. This example tests the %import directive and working with multiple modules.
  2. Use 'python runme.py' to run a test.
  3. Overview:
  4. ---------
  5. The example defines 4 different extension modules--each wrapping
  6. a separate C++ class.
  7. base.i - Base class
  8. foo.i - Foo class derived from Base
  9. bar.i - Bar class derived from Base
  10. spam.i - Spam class derived from Bar
  11. Each module uses %import to refer to another module. For
  12. example, the 'foo.i' module uses '%import base.i' to get
  13. definitions for its base class.
  14. If everything is okay, all of the modules will load properly and
  15. type checking will work correctly. Caveat: Some compilers, for example
  16. gcc-3.2.x, generate broken vtables with the inline methods in this test.
  17. This is not a SWIG problem and can usually be solved with non-inlined
  18. destructors compiled into separate shared objects/DLLs.
  19. Unix:
  20. -----
  21. - Run make
  22. - Run the test as described above
  23. Windows:
  24. --------
  25. - Use the Visual C++ 6 workspace file (example.dsw). Build the runtime
  26. project DLL first followed by the other 4 DLLs as they all have a
  27. dependency on the runtime DLL. The Batch build option in the Build menu
  28. is usually the easiest way to do this. Only use the Release builds not
  29. the Debug builds.
  30. - Run the test as described above