Skip to content

Migrate mostrobotpy to semiwrap #170

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

Open
wants to merge 70 commits into
base: main
Choose a base branch
from
Open

Migrate mostrobotpy to semiwrap #170

wants to merge 70 commits into from

Conversation

virtuald
Copy link
Member

@virtuald virtuald commented May 11, 2025

Copy link
Member

@TheTripleV TheTripleV left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are the native.* packages there to split off downloading libs from the wrapping? Will native.wpiutil be published to PyPI separately or be bundled into robotpy-wpiutil before publish?

@virtuald
Copy link
Member Author

virtuald commented May 16, 2025

They will be published to pypi separately. See #101 for history.

The download aspect is part of it, but really it's about the wpilib binaries being platform-specific and not interpreter specific. By having separate wheels we consume less space because it's not duplicated per-interpreter, and for wpimath in particular we are getting closer to our quota on pypi.

If we were able to use abi wheels this advantage would go away.

I'm not 100% sold on this change yet (or the naming for it), open to arguments against it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Publish allwpilib binaries in separate packages and use pkg-config .pc files
2 participants