![]() Thanks in advance for the : Thanks for pointing out the documentation for wheel format!Īs per the above documentation wheels have a list of required packages that are required for the wheel to run (along with version and platform tags). I’ve had to hack the spack compiler wrappers and remove automatic include paths from packages in the build dependency so I want to verify that everything works as I expect it to and the wheel that is built and installed links to the libraries we expect it to link to. ![]() numpy/ absl/… which is then installed via python setup.py install in the current spack recipe for py-tensorlfow. Bazel builds a wheel using some versions C/Python libraries viz. PS : I’m trying to understand this because I’m figuring out how the tensorflow build process works so as to integrate it into the spack package manager. whl file) using pip vs python setup.py install Is there any difference in installing a wheel (from a. Following up on the above, are these dependencies linked to at run time after a wheel is installed or during the installation phase ? How does a wheel find the dependencies it needs to run? I’ve built a wheel which depends on C/Python libraries (which get listed in the wheel as requirements) but the final wheel does not have the locations of the dependencies (I inspected the wheel with wheel-inspect). ![]() I’m trying to understand some things about installation from wheels. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |