File: README

package info (click to toggle)
swig 4.0.2-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 42,876 kB
  • sloc: cpp: 61,013; ansic: 27,612; java: 14,670; python: 10,632; cs: 8,103; makefile: 6,287; yacc: 6,197; sh: 5,247; ruby: 5,172; perl: 3,541; php: 2,069; ml: 2,066; lisp: 1,894; javascript: 1,300; tcl: 1,091; xml: 115
file content (10 lines) | stat: -rw-r--r-- 571 bytes parent folder | download 
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 the 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