eCAL Packages on PyPi about ecal HOT 5 OPEN

@DownerCase thanks for this great hint! Setuptools-protobuf seems really promising.
We have to see if it plays together with py-build-cmake, but worst case, we'll make two different packages, one with the binary extensions, and one with the _pb2 files, but let's see..

from ecal.

For windows x64 we should be PyPi ready, as Windows has the most amazing binary compatibility of all Operating systems. So there really isn't an issue with publishing .whl files containing native .dlls

For Linux we currently depend on too many system packages, I guess. The .whl files are just not self contained enough for being functional on a wide variety of Linux distros.

from ecal.

You've probably already done the investigation; but it is certainly possible to generate the pb files as part of setup.py, I've been able to do a PoC of that process. Mostly involves injecting an extra subcommand into the main build command.

You can look to Google's protobuf distutils and the newer (and pyproject compatible) setuptools-protobuf projects for inspiration (if they're not directly suitable).

from ecal.

That said I was commenting from a pure python standpoint.

Given you’re calling into a CMake build system you should be able to set up an add_custom_command to call protoc with the normal —python-out argument to generate the python bindings as part of the build.

from ecal.

The good thing is that during build, we already have protobuf available. That's challenging with setuptools-protobuf as the user has to provide a protoc (which needs to be compatible with the protobuf version that he wants to use).

from ecal.