I'm compiling a c++ program using
g++ -g -Wall -o my_binary -L/my/dir -lfoo bar.cpp
Add the path to where your new library is to
LD_LIBRARY_PATH (it has slightly different name on Mac ...)
Your solution should work with using the
-L/my/dir -lfoo options, at runtime use LD_LIBRARY_PATH to point to the location of your library.
Use the rpath option via gcc to linker - runtime library search path, will be used instead of looking in standard dir (gcc option):
This is good for a temporary solution. Linker first searches the LD_LIBRARY_PATH for libraries before looking into standard directories.
If you don't want to permanently update LD_LIBRARY_PATH you can do it on the fly on command line:
You can check what libraries linker knows about using (example):
/sbin/ldconfig -p | grep libpthread libpthread.so.0 (libc6, OS ABI: Linux 2.6.4) => /lib/libpthread.so.0
And you can check which library your application is using:
ldd foo linux-gate.so.1 => (0xffffe000) libpthread.so.0 => /lib/libpthread.so.0 (0xb7f9e000) libxml2.so.2 => /usr/lib/libxml2.so.2 (0xb7e6e000) librt.so.1 => /lib/librt.so.1 (0xb7e65000) libm.so.6 => /lib/libm.so.6 (0xb7d5b000) libc.so.6 => /lib/libc.so.6 (0xb7c2e000) /lib/ld-linux.so.2 (0xb7fc7000) libdl.so.2 => /lib/libdl.so.2 (0xb7c2a000) libz.so.1 => /lib/libz.so.1 (0xb7c18000)