Build python binding as regular package

[KernelA]

This pull request contains:

• GitHub workflow to build python package for Linux only
• publishing it on the release page when tag a commit
• new doc for python binding

Release page example

We can install python binding as regular python package via pip. I think it simplifies package using and will lead to more broadly using.

The workflow contains code for windows building, but I cannot compile it with MS MPI. Changes in the source code are needed.

[ethzasl-jenkins]

Can one of the admins verify this patch?

[pomerlef]

ok to test

[pomerlef]

@aguenette can you have a look?

[pomerlef]

@KernelA , this is a great add-on for libpointmatcher!

We are not set up to use GitHub workflow yet, but the timing is good as our legacy CI tool seems to stop working. Hopefully, by mid-summer, we will have transitioned to GitHub workflow. Don't give up, your PR will be processed ;)

[KernelA]

@pomerlef, ok. I think there is some work. For example, extracting version from CMake file as base version for the python package. We must sync it manually, at the moment.

[RedLeader962]

@KernelA By the way awesome work. It is a great addition to libpointmatcher.

[RedLeader962]

I've finish my review and added my recommandation. Good job @KernelA, this is going to be very useful for the build system automation.

Remark: I've tested the GitHub workflow using nektos/act.

Note to self: we will have to refactor the jobs steps eventualy to reduce build time if we want to add support for other ubuntu versions and computer architecture (boost and libnabo install could go in a docker container) but this pull request is a great starting point.

Thanks @KernelA

[RedLeader962]

Fetching the pointmatcher version dynamicaly will be a very usefull tool for the build system automation.
(!) Limitation: This approach to fetching the POINTMATCHER_VERSION only work if the user execute

python -m build --wheel

It will break when using the default

python -m build

because the build command will build sdist in a first step and then build wheel fetching from a temporary dir /tmp/build-via-sdist-*/pypointmatcher-*.

I recommand

• to keep this approach for now but wrapped in a try/except clause with an explicit error message pinpointing its origin since it is not obvious when it happen in a install stacktrace which is usualy prety long;
• to add an explicit comment on those limitations in the code to advise futur developer;
• and to add a warning in the doc/CompilationPython.md package install procedure.

[KernelA]

@RedLeader962, thank you for feedback! I did make changes according to review.

Will wait a build status:
https://github.com/phygitalism/libpointmatcher/actions/runs/4952671666

[KernelA]

The last build status:
https://github.com/phygitalism/libpointmatcher/actions/runs/4966179029

[RedLeader962]

Ready to merge PR.
@pomerlef Will need to bypass Jenkins

@KernelA Good job