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
We have an externally imported package (OpenUSD) which I build independently with python 3.11, and whose libraries depend on libpython3.11.dylib. But when I run otool -l on libpython3.11.dylib that I get (from here, I found) , I get, in part:
Load command 4
cmd LC_ID_DYLIB
cmdsize 64
name /install/lib/libpython3.11.dylib (offset 24)
time stamp 1 Wed Dec 31 16:00:01 1969
current version 3.11.0
compatibility version 3.11.0
Eventually, this causes a runtime crash, because that path doesn't exist. Seems to me that a library that is part of a standalone distribution ought to be relocatable (and thus I'd expect @rpath/libpython3.11.dylib for LC_ID_DYLIB). Unless I'm going down the entirely wrong path.
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
-
We have an externally imported package (OpenUSD) which I build independently with python 3.11, and whose libraries depend on libpython3.11.dylib. But when I run
otool -l
onlibpython3.11.dylib
that I get (from here, I found) , I get, in part:Eventually, this causes a runtime crash, because that path doesn't exist. Seems to me that a library that is part of a standalone distribution ought to be relocatable (and thus I'd expect
@rpath/libpython3.11.dylib
forLC_ID_DYLIB
). Unless I'm going down the entirely wrong path.Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions