Replies: 2 comments
-
You need to tell your build backend to include these libraries in the original wheel. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks! That's what I was missing. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When I use auditwheel to copy libraries into my wheel, it renames all of them, adding unique hashes to them. This breaks my wheel: the names of the libraries are part of the public interface. They're being distributed with the expectation that other programs will link against them. How can I prevent that from happening?
As an example of what I want to do, if I
pip install torch
and then look insidesite-packages/torch/lib
, the libraries have ordinary names likelibtorch.so
andlibc10.so
, notlibtorch-12345678.so
. I want to do the same thing with my package.Beta Was this translation helpful? Give feedback.
All reactions