You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm planning to move all my robotpy projects to meson, but hadn't really figured out the best way to make inter-wheel dependencies work -- so I'm glad I found this!
Background
My dependencies are built and published to a maven-like repo + artifacts. I take those, build pybind11 wrappers around them, and stick it all in a wheel that depends on other wheels (described here).
As part of this move to meson, I think what would make the most sense is for me to write a tool that gets the maven artifact, unzips it, adds a .pc file and entrypoint, and then publishes that wheel to pypi. Then all of my wrapper wheels can just specify the wheel that just has the native dependency in it in their build dependencies, and meson will magically find it and everything works.
The question
It seems to me that there are probably other people that would like to take binary artifacts and repackage them as wheels that can be consumed by something that uses pkg-config.
Does such a tool already exist?
If not, I'm going to write said tool, because I need it. Is there any interest in that tool living either in this repo, or another pypackaging-native repo?
I'm also open to alternative solutions as well.
The text was updated successfully, but these errors were encountered:
I'm planning to move all my robotpy projects to meson, but hadn't really figured out the best way to make inter-wheel dependencies work -- so I'm glad I found this!
Background
My dependencies are built and published to a maven-like repo + artifacts. I take those, build pybind11 wrappers around them, and stick it all in a wheel that depends on other wheels (described here).
As part of this move to meson, I think what would make the most sense is for me to write a tool that gets the maven artifact, unzips it, adds a .pc file and entrypoint, and then publishes that wheel to pypi. Then all of my wrapper wheels can just specify the wheel that just has the native dependency in it in their build dependencies, and meson will magically find it and everything works.
The question
It seems to me that there are probably other people that would like to take binary artifacts and repackage them as wheels that can be consumed by something that uses pkg-config.
I'm also open to alternative solutions as well.
The text was updated successfully, but these errors were encountered: