swig/relativeimport2 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
..
py2	Replace cd X && $(MAKE) with $(MAKE) -C X	2024-09-21 11:24:02 +12:00
py3	Replace cd X && $(MAKE) with $(MAKE) -C X	2024-09-21 11:24:02 +12: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 -relativeimport option.

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

Overview:
---------

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

     pyX/pkg2/pkg3/pkg4/foo.i  - Pkg4_Foo class
     pyX/pkg2/bar.i            - Pkg2_Bar class derived from Pkg4_Foo

The difference between this ('relativeimport2') case and the case
'relativeimport1' is the "distance" between importer and importee.

If everything works well, the package pyX.pkg2 shall load properly.

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