swig/same_modnames1 at 2f00a7dc07c5c19fcd224c6054c9d444f2a76ab2 - swig

History

Olly Betts 250be3883d Replace cd X && $(MAKE) with $(MAKE) -C X We require GNU make anyway, and using -C reduces the verbosity of the code a little and allows us to avoid an extra subshell in some cases.		2024-09-21 11:24:02 +12:00
..
pkg1	Remove use of preinst-swig script	2015-08-21 22:43:17 +01:00
pkg2	Remove use of preinst-swig script	2015-08-21 22:43:17 +01:00
Makefile	Replace cd X && $(MAKE) with $(MAKE) -C X	2024-09-21 11:24:02 +12:00
README	Fixed SF bug #1297 (Python imports)	2013-12-24 17:22:25 +00:00
runme.py	Fix various typos	2022-04-11 07:59:36 +12:00

README

This example tests the %import directive and working with multiple modules.

There are two modules having same name but belonging to different packages.
This case is not correctly handled by swig 2.

The issue was reported as Source Forge bug #1297 and later as GitHub issue #7.

Use 'python runme.py' to run a test.

Overview:
---------

The example defines 2 different extension modules--each wrapping a separate C++
class.

  pkg1/foo.i - Pkg1_Foo class.
  pkg2/foo.i - Pkg2_Foo class (derived from Pkg1_Foo).

The pkg2/foo.i module uses %import to refer to pkg1/foo.i.

If everything works well, the module pkg2.foo shall load properly.

Unix:
-----
- Run make
- Run the test as described above.