pyrobuf
pyrobuf copied to clipboard
modules get rebuilt when generating a source distribution
When I run python setup.py sdist
to generate a source distribution for PyPI, I notice that it triggers a build of the proto items listed in the pyrobuf_modules
keyword arg in the setup.py file. I do not expect binary artefacts to be getting (re)built during a source package generation.
This does not stop me from creating the source distribution - its more of an annoyance and wastes some time.
I've got a similar situation: I want to provide a package to other machines which don't necessarily have a c++-compiler. Is it possible to provide a switch, to select if a new build of the proto files should be triggered or just installed from the out / build dir?
@claws, I think this would also help your problem.