I'm building compartmentalized systems on servers. There may be several
systems with different setups, thus library management is important.
I'm wondering why libgdal looks like this
readelf -d parts/gdal/lib/libgdal.so
0x0000000000000001 (NEEDED) Shared library: [libgeos_c.so.1]
0x0000000000000001 (NEEDED) Shared library: [libexpat.so.1]
0x0000000000000001 (NEEDED) Shared library: [libgeotiff.so.2]
0x0000000000000001 (NEEDED) Shared library: [libproj.so.0]
0x0000000000000001 (NEEDED) Shared library: [libtiff.so.3]
0x0000000000000001 (NEEDED) Shared library: [libpthread.so.0]
0x0000000000000001 (NEEDED) Shared library: [libxml2.so.2]
0x0000000000000001 (NEEDED) Shared library: [libz.so.1]
0x0000000000000001 (NEEDED) Shared library: [libiconv.so.2]
0x0000000000000001 (NEEDED) Shared library: [libdl.so.2]
0x0000000000000001 (NEEDED) Shared library: [libstdc++.so.6]
0x0000000000000001 (NEEDED) Shared library: [libm.so.6]
0x0000000000000001 (NEEDED) Shared library: [libc.so.6]
0x0000000000000001 (NEEDED) Shared library: [libgcc_s.so.1]
0x000000000000000e (SONAME) Library soname: [libgdal.so.20]
0x000000000000001d (RUNPATH) Library runpath:
[/home/ajolma/fims-server/parts/expat/lib:/home/ajolma/fims-server/parts/libxml2/lib]
when GDAL was built with
--with-libtiff=/home/ajolma/fims-server/parts/tiff, i.e., why the
libtiff directory did not get into RUNPATH?
LD_LIBRARY_PATH can be used to make libtiff found from the correct
location but it is an extra hassle.
Ari
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
