dependency injection - gcc linking of shared libraries: secondary dependencies with $ORIGIN -
this follow-up question this one.
i understand using $origin in -rpath option generates dynamic absolute path point specified location - no matter use library.
what's confusing me, following: use library generate shared binary , set (again) -wl,-rpath option using $origin enable binary find library. original $origin value of library not available anymore or wrong because seems overwritten new one.
somehow understandable since generating new shared object - binary - has own $origin. way around this, provide binary's -rpath both locations, 1 library , 1 library needs. in opinion makes -rpath useless, because can't link library , specify location need specify library's dependency location.
my question: there way specify hierarchical -rpath values using $origin? avoid absolute paths, fix issue.
 
 
  
Comments
Post a Comment