File: README

package info (click to toggle)
swig 4.3.0-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 46,244 kB
  • sloc: cpp: 54,631; ansic: 29,123; java: 17,530; python: 12,505; cs: 10,369; ruby: 7,232; yacc: 6,477; makefile: 5,965; javascript: 5,520; sh: 5,415; perl: 4,187; php: 3,693; ml: 2,187; lisp: 2,056; tcl: 1,991; xml: 115
file content (10 lines) | stat: -rw-r--r-- 567 bytes parent folder | download | duplicates (3) 
1
2
3
4
5
6
7
8
9
10
 
  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