Bindings generation

As mentioned in Subsection 11.3.1, Python must have been compiled as a shared or dynamically linked library. To implement an object in Python, Babel must first create the Python implementation-side bindings12.2 as follows$:$

% babel -exclude-external -server=python file.sidl
or simply
% babel -E -s=python file.sidl

This creates the IOR, Python skeletons (i.e., _pSkel.c), and Python launch (i.e., _pLaunch.c) files in the current directory. In most cases, the IOR, _pSkel.c, and _pLaunch.c files must be compiled and place in a shared library. It also creates a tree of subdirectories based on the package hierarchy found in file.sidl in which it generates Python extension modules for the client-side binding (i.e., _Module.c) and implementation (i.e., _Impl.py) files. The implementation files need to be filled in, as described in Subsection 11.4.2, and extension modules compiled as discussed in Subsection 11.4.3.





babel-1.4.0
users_guide Last Modified 2008-10-16

http://www.llnl.gov/CASC/components
components@llnl.gov