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
My question is how a ${package}.libs dir is created or not.
The wheel building is currently set-up to copy the shared libraries into ${package}/libs, but I've found that auditwheel will duplicate these libraries into ${package}.libs (xref Toblerity/rtree#270). My solution was to delete the duplicated ${package}/libs. I've recently refactored the build by setting CMAKE_INSTALL_RPATH to "\$ORIGIN" because there are two .so files that share a dependency (xref Toblerity/rtree#316) but now auditwheel isn't creating ${package}.libs. So what controls this behavior? Suggestions welcome!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm maintaining https://github.com/Toblerity/rtree, which is a pure Python package that embeds platform-specific shared libraries into binary wheels, using them via ctypes.
My question is how a
${package}.libsdir is created or not.The wheel building is currently set-up to copy the shared libraries into
${package}/libs, but I've found that auditwheel will duplicate these libraries into${package}.libs(xref Toblerity/rtree#270). My solution was to delete the duplicated${package}/libs. I've recently refactored the build by setting CMAKE_INSTALL_RPATH to"\$ORIGIN"because there are two.sofiles that share a dependency (xref Toblerity/rtree#316) but now auditwheel isn't creating${package}.libs. So what controls this behavior? Suggestions welcome!Beta Was this translation helpful? Give feedback.
All reactions