14 июл. 2009 г. · Since ldd lists only the dynamic libraries, is there a way to extract the information about the static libraries used to create the executable?

30 июн. 2014 г. · ldd shows which shared libraries a library or executable needs. In this case none, because libddv3djava.so is statically linked.

11 апр. 2019 г. · This is going to be a nightmare. You need static versions of all these libraries (*.a files instead of *.so files).

24 июл. 2021 г. · I'm trying to create a shared library object (which will be loaded into R using dlopen) which links to the static rather than the dynamic version of a third- ...

29 дек. 2018 г. · Not necessarily. You can create a shared library with no dependencies but with undefined symbols. Such a library will work fine if the symbols are provided by ...

24 янв. 2013 г. · If you want to force the linker to use the static version of a particular library you can use the :filename to force a particular library ...

28 мая 2011 г. · There is one omniorb library which I want to link dynamically. Currently I have dynamically linked all the libraries. ldd shows the following

12 июн. 2019 г. · I place a compiled libfoo.a into relative directory libs, and write: g++ mycode -L libs -lfoo to my surprise, the executable size does not change.

24 нояб. 2016 г. · For a static library (.a file), how to list the module-level dependencies of it? I know for a shared library (.so), we can use objdump or readelf to do this.

13 нояб. 2022 г. · Run the ldd program on the generated executable(s). This will give you a list of all the shared libraries that are dynamically linked to it.