-
saubatn authored
Create a parallel tree of the SDK which is CMake-configured only if CAMITK_BINDING_PYTHON variable is manually set to true (default is OFF) Each directory on that tree contains : * a typesystem.xml file that contains the local folder C++ classes to expose to Python. * a global.h C++ header file required to correclty include the C++ classes to expose. Both these files are recursively including their subdirectories correspondanding files. This allows Shiboken to be only run on the top python_sdk directory, but keep specifying the classes to expose to Python in the corresponding local typesystem.xml / global.h files in the tree (better to understand / maintain). On top of the python_sdk directory is created the custom sdk_wrap_to_python CMake target, which allows to run shiboken on the top python_sdk folder's typesystem.xml / global.h and thus make the SDK binding. Coming soon : another target would be created in order to compile the wrapped shiboken-generated C++ classes and link them with the originale CamiTK SDK C++ library in order to produce the CPython extension, i.e. the Python package of CamiTK sdk. Coming soon : debugging (of course ;-) ) git-svn-id: svn+ssh://scm.forge.imag.fr/var/lib/gforge/chroot/scmrepos/svn/camitk/trunk/camitk@1170 ec899d31-69d1-42ba-9299-647d76f65fb3
0fe41901