-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build python wheels #171
Build python wheels #171
Conversation
4d7eeb8
to
a7b50cb
Compare
1b3def0
to
c5e8ebb
Compare
ed91636
to
062178d
Compare
209c798
to
8211be3
Compare
8211be3
to
ce82c25
Compare
@@ -30,6 +30,7 @@ fn compile_protos() { | |||
)); | |||
} | |||
|
|||
/* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this broken under CI?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TLDR yes - for examplearduino/setup-protoc
doesn't support windows and official protoc binaries for windows are not available.
IMO we should remove protoc from the build step, but I didn't want to do that here. We can either commit the compiled protos to git (like we're doing with all other libraries in this repo), or even better we can remove proto serialization from the python sdk entirely and let rust handle it.
https://linear.app/foxglove/issue/FG-10358/spike-python-protobuf-serialization-in-rust
Changelog
None
Docs
None
Description
Our upcoming python sdk uses maturin to depend on rust code. Most python users will want to install from wheels, containing the precompiled rust binaries.
This PR adds support for compiling wheels on 86 different operating systems and architectures.
Python jobs are moved to a separate workflow because
ci.yml
was getting out of hand. We could potentially separate the remaining ROS + Rust + TypeScript workflows into separate files in the future too.