Based on an IRC conversation today; this applies to cmake-extra-modules (which contains the CMake-fu for Python bindings generation) and kitemmodels (which use that -fu to generate bindings). The idea is to sort out the toolchain for target distributions -- there seem to be Ubuntu-specific things in there.
Source material: https://steveire.wordpress.com/2016/05/18/generating-python-bindings-with-clang/
- does ecm_generate_python_binding() work for everyone?
- does it handle LLVM versioning?
- does it handle Python versioning?
Related bugs:
Distro-raised issues:
- properly detect the python install path and the clang library name via cmake-foo. // The hack on stackoverflow seems to work http://stackoverflow.com/questions/1242904/finding-python-site-packages-directory-with-cmake But I'd be surprised if that's really the least-awful way to do it. (doesn't *quite* work on Arch, because it assumes 'python' to be python2)
- the clang code also seems to need fixing for FreeBSD, something on the lines of find_library(libclang_LIBRARY clang PATHS /usr/local/llvm3${_LIBCLANG3_FIND_VERSION}/lib )