-
Notifications
You must be signed in to change notification settings - Fork 25
Closed
Description
The wheel can be used in two scenarios:
- in a project which will depend on
import scipy_openblas64to load the shared object into the executable and make the symbols available without the runtime loader needing to find the shared object - in a project which will not depend on the wheel at runtime, so it will have to ship the shared object and it can be loaded at runtime via a
NEEDEDdirective in the shared object that consumes the symbols
The second method is the one currently used by NumPy/SciPy. The difference between the two is
- The first options requires something like the
_distributor_init.pytrick to callimport scipy_openblas at runtime. It also requires that thescipy-openblas.pcfile have an emptyLibs:` line (on posix). - The second option will use something like
auditwheelto pack the shared object into the project wheel, so it needs a properLibs: -L${libdir} -l scipy_openblas64_line in thescipy-openblas.pcfile
I think this can be resolved by adding an argument to get_pkg_config() to specify which line to create. Any good thoughts for what that argument should be called?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels