Hi @matthewfeickert @agoose77 so, (with the stressed disclaimer that i still lack a lot of knowledge about the python ecosystem) i found these bits of info:
RPATH vs RUNPATH : RPATH is search before LD_LIBRARY_PATH while RUNPATH after it.
so i would say, that for python bindings RPATH should be used and pointing to the xrootd binary libs from $(python3 -m site --user-site)/pyxrootd/lib64
lib64 on rhel family, lib on debian family. this way, the libraries will always be found and we can avoid any problems given by LD_LIBRARY_PATH (the python bindings come as a package, we should not risk any mixing of some other versions)
i'm not sure how $ORIGIN is supposed to work as RUNPATH, as this is the location of an executable, but what is the executable in this case?
wheel vs egg : before some fancy/new/latest building tools (pybind11/scikit-build) that would be required to work on centos7/python3.6 i think that we should establish why is egg used instead of wheel .. from what i see in packaging/wheel/publish.sh a sdist wheel should be created not an egg one .. so, anyone any idea what is going on?
Thanks a lot!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1