Add Pip Package Release Pipeline #6
Description
Issue:
- the current package installation relies on a "source distribution" which requires building the source code on client-side
- this is really annoying because building sources requires to have C/C++ compiler toolchain installed, etc.
- a much nicer way would be uploading pre-compiled, highly-compatible pip packages
- creating the pip packages can be automatically triggered whenever a feature branch is merged into origin/master
Suggested Solution:
- in the Dockerfile, CMake seems to be creating a working python libraray (.so file)
- figure out how to create python wheels (.whl) from the build output (consider e.g. scikit-build as it supports CMake)
- then, extend the procedure for common manylinux build environments to target various OS and python versions
- therefore use the official manylinux build envs provided as Docker images on quay.io, see https://github.com/pypa/manylinux
- for targeting Windows, use a Windows Docker image for the GitHub workflow (OS targeting shouldn't be so complicated here)