packaging advice for cmake generated python wrapper

[Ghislain Vaillant <ghisvail@gmail.com>]

Hi guys,

I am currently trying to package the ISMRMRD library (#732360), which
uses cmake for its build system and generates the c++ library and
corresponding Java and Python wrappers using SWIG.

I was wondering how that would play along with Debian packaging and what
would be the best approach for it. I am also in close relationship with
upstream and they are inclined to modify the existing cmake files to
ease support for Debian packaging.

With the current set-up, cmake generates both the java and Python
wrappers and the library in the same target folder, i.e. after make, all
resulting binaries are all stored in /usr/local/ismrmrd/lib/ which
includes libismrmrd.so (shlib), ismrmrd.jar (java wrapper), ismrmrd.so,
ismrmrd.py (python wrapper). Besides, cmake only builds the python
wrappers for Python 2 via SWIG.

I have packaged python-only projects before, using the convenience
offered by setup.py and setuptools. However for that case, I am a
clueless and did not find much documentation or similar case to study
on.

Any advice on packaging / fixing the build system for this library would
be warmly welcome.

Thanks,

Ghislain