swig/Examples/python/import_packages/split_modules
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
..
vanilla Replace cd X && $(MAKE) with $(MAKE) -C X 2024-09-21 11:24:02 +12:00
vanilla_split 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 Fix a few documentation typos 2022-09-29 18:17:32 +13:00

README

  These examples/tests are for when the SWIG generated wrapper module is split
between two packages.  Specifically the pure python part is part of a package
and the C/C++ part is not in any package at all.  Historically SWIG has
supported this sort of thing.
From SWIG 4.0.0 onwards, split modules are not supported by default.
The %module directive needs to be customised with the moduleimport attribute
in order to import a global C/C++ module.

vanilla        # "plane Jane" module both halves in pkg1
vanilla_split  # python 1/2 in pkg1 C 1/2 in global namespace