Timeline for How do you specify the location of libraries to a binary? (linux)
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 29, 2017 at 21:13 | comment | added | Ethan | yeah, in my case I was wanting to test a package by linking against its build directory rather than installing it... (but the package had several internal .so's with some inter-dependencies... variety of workarounds but just annoying) | |
| May 28, 2017 at 20:08 | comment | added | ttsiodras |
@Ethan: True. But what's also true is that the usual scenarios where you want to "package" shared libraries for some binary, is one where you placed them all together; e.g. /opt/mypackage/bin/someBinary will need libs that you store in /opt/mypackage/lib/. Pretty much all proprietary SW installed under /opt follows this rule - which means that the way shown above will cover all such installs. They will then usually add also a symlink under /usr/bin that points to the binary under /opt - knowing that the "default search path" will find the .sos under the appropriate /opt/.../lib folder.
|
|
| May 27, 2017 at 18:56 | comment | added | Ethan | But if the library in question itself has shared libraries to look up, the rpath stored in the binary isn't applied recursively to the sub-library lookups. I haven't found a way around this other than setting LD_LIBRARY_PATH in the environment, which then does get applied to recursive lookups... | |
| Jun 1, 2016 at 12:58 | history | edited | ttsiodras | CC BY-SA 3.0 |
Moved my site.
|
| Sep 25, 2010 at 16:10 | history | answered | ttsiodras | CC BY-SA 2.5 |